Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last sightingsame day
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Oct 13, 2026
- EUVDENISA, European Unionlisted Oct 13, 2026
- VulnCheck KEVcommercial researchlisted Oct 13, 2026
- CIRCLaggregator, mirrors the abovelisted Oct 13, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationapi.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Oct
- reported exploitationmsrc.microsoft.com/update-guide/vulnerability/CVE-2026-96951
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
3 public reports collected from VulnCheck and CIRCL, first on Oct 13, 2026. Each links to its original source. We have not verified them.
Description
Microsoft Windows Shell contains a command injection vulnerability that allows an unauthorized attacker to bypass a security feature over a network.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.