Verified reference description
The following technical description is credited to the CISA KEV dataset (CC0):
Microsoft Windows Shell contains a command injection vulnerability that allows an unauthorized attacker to bypass a security feature over a network.
Record and timeline
- Product: Microsoft — Windows
- Identifier: CVE-2026-96951
- CVE record published: 2026-10-13
- Added to CISA KEV: 2026-10-13
- Reference score: 8.8/10, CVSS 3.1; provider: microsoft
- Weakness class: CWE-77
A KEV addition date is not a discovery date. CVSS describes technical severity; actual exposure and asset importance also influence remediation priority.
Defensive next steps
Match the installed Microsoft Windows version and configuration against the linked technical advisory. Apply the manufacturer-approved fixed release or an explicitly documented mitigation; this profile does not guess a fixed version. Verify the patch and review relevant logs afterward. Plan a supported replacement where the product is end-of-life.
Scope and limitations
This is an awareness and defensive-prioritization profile, not a penetration test or a finding that your network is compromised. KEV membership indicates evidence of real-world exploitation. Mandatory CISA deadlines apply to entities covered by the relevant directive, not universally to every reader.
Reported versions and platforms
The table shows up to ten structured version entries from the official CVE-2026-96951 record. Original field names and values are retained deliberately. This is not an automated exposure verdict or a complete list of every product branch; use the full record and vendor advisory for a deployment decision.
| Product in record | Platform | Version fields — original values | Record status |
|---|---|---|---|
| Microsoft — Outlook.com | — | version=1.0.0; lessThan=20260925.100; versionType=custom | affected |
| Microsoft — Windows 10 Version 1607 | 32-bit Systems, x64-based Systems | version=10.0.14393.0; lessThan=10.0.14393.9612; versionType=custom | affected |
| Microsoft — Windows 10 Version 1809 | 32-bit Systems, x64-based Systems | version=10.0.17763.0; lessThan=10.0.17763.9376; versionType=custom | affected |
| Microsoft — Windows 10 Version 21H2 | 32-bit Systems, ARM64-based Systems, x64-based Systems | version=10.0.19044.0; lessThan=10.0.19044.7807; versionType=custom | affected |
| Microsoft — Windows 10 Version 22H2 | 32-bit Systems, ARM64-based Systems, x64-based Systems | version=10.0.19045.0; lessThan=10.0.19044.7807; versionType=custom | affected |
| Microsoft — Windows 11 version 23H2 | ARM64-based Systems | version=10.0.22631.0; lessThan=10.0.22631.7652; versionType=custom | affected |
| Microsoft — Windows 11 Version 23H2 | x64-based Systems | version=10.0.22631.0; lessThan=10.0.22631.7652; versionType=custom | affected |
| Microsoft — Windows 11 Version 24H2 | ARM64-based Systems, x64-based Systems | version=10.0.26100.0; lessThan=10.0.26100.9711; versionType=custom | affected |
| Microsoft — Windows 11 Version 25H2 | ARM64-based Systems, x64-based Systems | version=10.0.26200.0; lessThan=10.0.26200.9711; versionType=custom | affected |
| Microsoft — Windows 11 version 26H1 | ARM64-based Systems, x64-based Systems | version=10.0.28000.0; lessThan=10.0.28000.3231; versionType=custom | affected |
Full record and technical references
Turn the record into an operational decision
For Microsoft Windows, record the asset, effective version, enabled feature and access path. When the reference does not map clearly to your package or branch, retain an explicit unknown status and assign follow-up rather than guessing that the system is safe.
After remediation, record the effective running version, health-check outcome and change time, not merely installation success. Evidence of compromise requires the appropriate incident-response workflow; this page does not diagnose any network as compromised or clean.
Scoring vector and scope
Vector recorded by the reference: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
CVSS is owned by FIRST and used by permission. The reference score is not a substitute for organizational risk assessment. Version data comes from the record retrieved for this review and may change when sources are updated.
