Windows Shell Security Feature Bypass Vulnerability
Protection mechanism failure in Windows Shell allows an unauthorized attacker to bypass a security feature over a network.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Apr 14, 2026
- Updated
- Sep 25, 2026
- EPSS
- 0.8% · 56th percentile
- CWE
- CWE-693
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 21h2 | cpe:2.3:o:microsoft:windows_10_21h2 |
| microsoft | windows 10 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows 11 24h2 | cpe:2.3:o:microsoft:windows_11_24h2 |
| microsoft | windows 11 25h2 | cpe:2.3:o:microsoft:windows_11_25h2 |
| microsoft | windows 11 26h1 | cpe:2.3:o:microsoft:windows_11_26h1 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows server 2022 | cpe:2.3:o:microsoft:windows_server_2022 |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 2012all versions
- microsoft windows server 2012r2
- microsoft windows server 2016before 10.0.14393.9060
- microsoft windows server 2019before 10.0.17763.8644
- microsoft windows server 2022before 10.0.20348.5020
- microsoft windows server 2022 23h2before 10.0.25398.2274
- microsoft windows server 2025before 10.0.26100.32690
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows 10 Version 1607
- 10.0.14393.0 and later · before 10.0.14393.9060affected
Microsoft Windows 10 Version 1809
- 10.0.17763.0 and later · before 10.0.17763.8644affected
Microsoft Windows 10 Version 21H2
- 10.0.19044.0 and later · before 10.0.19044.7184affected
Microsoft Windows 10 Version 22H2
- 10.0.19045.0 and later · before 10.0.19045.7184affected
Microsoft Windows 11 version 22H3
- 10.0.22631.0 and later · before 10.0.22631.6936affected
Microsoft Windows 11 Version 23H2
- 10.0.22631.0 and later · before 10.0.22631.6936affected
Microsoft Windows 11 Version 24H2
- 10.0.26100.0 and later · before 10.0.26100.8246affected
Microsoft Windows 11 Version 25H2
- 10.0.26200.0 and later · before 10.0.26200.8246affected
Microsoft Windows 11 version 26H1
- 10.0.28000.0 and later · before 10.0.28000.1836affected
Microsoft Windows Server 2012
- 6.2.9200.0 and later · before 6.2.9200.26026affected
Microsoft Windows Server 2012 (Server Core installation)
- 6.2.9200.0 and later · before 6.2.9200.26026affected
Microsoft Windows Server 2012 R2
- 6.3.9600.0 and later · before 6.3.9600.23132affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-8174A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka "Windows VBScript Engine RemKEV86Now
- CVE-2022-44698Windows SmartScreen Security Feature Bypass VulnerabilityKEV74This week
- CVE-2026-21510Windows Shell Security Feature Bypass VulnerabilityKEV72This week
- CVE-2026-21513MSHTML Framework Security Feature Bypass VulnerabilityKEV70This week
- CVE-2023-24880Windows SmartScreen Security Feature Bypass VulnerabilityKEV70This week
- CVE-2026-33824Windows Internet Key Exchange (IKE) Service Extensions Remote Code Execution VulnerabilityKEV69This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-2151063 days apartWindows Shell Security Feature Bypass VulnerabilityKEV72This week
- CVE-2026-2151363 days apartMSHTML Framework Security Feature Bypass VulnerabilityKEV70This week
- CVE-2026-322020 days apartWindows Shell Spoofing VulnerabilityKEV48Plan
- CVE-2026-4558856 days apartSecure Boot Security Feature Bypass Vulnerability31Monitor
- CVE-2026-4765656 days apartWindows Boot Manager Security Feature Bypass Vulnerability31Monitor
- CVE-2026-4857056 days apartSecure Boot Security Feature Bypass Vulnerability31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.