CVE-2024-26194: Secure Boot Security Feature Bypass Vulnerability
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Windows 10 for 32-bit Systems 10.0.10240.20596; Windows 10 for x64-based Systems 10.0.10240.20596; Windows 10 Version 1607 for 32-bit Systems 10.0.14393.6897.
Low priority for now. Upgrade to Windows 10 for 32-bit Systems 10.0.10240.20596; Windows 10 for x64-based Systems 10.0.10240.20596; Windows 10 Version 1607 for 32-bit Systems 10.0.14393.6897 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Apr 9, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-347
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.4
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows 10 1507 | cpe:2.3:o:microsoft:windows_10_1507 |
| 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 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows server 2008 | cpe:2.3:o:microsoft:windows_server_2008 |
| 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 |
| microsoft | windows server 2022 23h2 | cpe:2.3:o:microsoft:windows_server_2022_23h2 |
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 1507
- 10.0.10240.0 and later · before 10.0.10240.20596affected
Microsoft Windows 10 Version 1607
- 10.0.14393.0 and later · before 10.0.14393.6897affected
Microsoft Windows 10 Version 1809
- 10.0.17763.0 and later · before 10.0.17763.5696affected
- 10.0.0 and later · before 10.0.17763.5696affected
Microsoft Windows 10 Version 21H2
- 10.0.19043.0 and later · before 10.0.19044.4291affected
Microsoft Windows 10 Version 22H2
- 10.0.19045.0 and later · before 10.0.19045.4291affected
Microsoft Windows 11 version 21H2
- 10.0.0 and later · before 10.0.22000.2899affected
Microsoft Windows 11 version 22H2
- 10.0.22621.0 and later · before 10.0.22621.3447affected
Microsoft Windows 11 version 22H3
- 10.0.22631.0 and later · before 10.0.22631.3447affected
Microsoft Windows 11 Version 23H2
- 10.0.22631.0 and later · before 10.0.22631.3447affected
Microsoft Windows Server 2008 Service Pack 2
- 6.0.6003.0 and later · before 6.0.6003.22618affected
Microsoft Windows Server 2008 R2 Service Pack 1
- 6.1.7601.0 and later · before 6.1.7601.27067affected
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
- 6.1.7601.0 and later · before 6.1.7601.27067affected
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 2008all versions
- microsoft windows server 2008r2
- microsoft windows server 2012all versions
- microsoft windows server 2012r2
- microsoft windows server 2016before 10.0.14393.6897
- microsoft windows server 2019before 10.0.17763.5696
- microsoft windows server 2022before 10.0.20348.2402
- microsoft windows server 2022 23h2before 10.0.25398.830
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34527Windows Print Spooler Remote Code Execution VulnerabilityKEV95Now
- CVE-2021-40444Microsoft MSHTML Remote Code Execution VulnerabilityKEV94Now
- CVE-2023-36025Windows SmartScreen Security Feature Bypass VulnerabilityKEV92Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26183Apr 9, 2024 · Windows Kerberos Denial of Service Vulnerability27Monitor
- ← EarlierCVE-2024-26189Apr 9, 2024 · Secure Boot Security Feature Bypass Vulnerability32Monitor
- Later →CVE-2024-26200Apr 9, 2024 · Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Windows 10 for 32-bit Systems | 10.0.10240.20596 · KB5036925 | Microsoft (MSRC) |
| Windows 10 for x64-based Systems | 10.0.10240.20596 · KB5036925 | Microsoft (MSRC) |
| Windows 10 Version 1607 for 32-bit Systems | 10.0.14393.6897 · KB5036899 | Microsoft (MSRC) |
| Windows 10 Version 1607 for x64-based Systems | 10.0.14393.6897 · KB5036899 | Microsoft (MSRC) |
| Windows 10 Version 1809 for 32-bit Systems | 10.0.17763.5696 · KB5036896 | Microsoft (MSRC) |
| Windows 10 Version 1809 for ARM64-based Systems | 10.0.17763.5696 · KB5036896 | Microsoft (MSRC) |
| Windows 10 Version 1809 for x64-based Systems | 10.0.17763.5696 · KB5036896 | Microsoft (MSRC) |
| Windows 10 Version 21H2 for 32-bit Systems | 10.0.19044.4291 · KB5036892 | Microsoft (MSRC) |
| Windows 10 Version 21H2 for ARM64-based Systems | 10.0.19044.4291 · KB5036892 | Microsoft (MSRC) |
| Windows 10 Version 21H2 for x64-based Systems | 10.0.19044.4291 · KB5036892 | Microsoft (MSRC) |
| Windows 10 Version 22H2 for 32-bit Systems | 10.0.19045.4291 · KB5036892 | Microsoft (MSRC) |
| Windows 10 Version 22H2 for ARM64-based Systems | 10.0.19045.4291 · KB5036892 | Microsoft (MSRC) |
| Windows 10 Version 22H2 for x64-based Systems | 10.0.19045.4291 · KB5036892 | Microsoft (MSRC) |
| Windows 11 version 21H2 for ARM64-based Systems | 10.0.22000.2899 · KB5036894 | Microsoft (MSRC) |
| Windows 11 version 21H2 for x64-based Systems | 10.0.22000.2899 · KB5036894 | Microsoft (MSRC) |
| Windows 11 Version 22H2 for ARM64-based Systems | 10.0.22621.3447 · KB5036893 | Microsoft (MSRC) |
| Windows 11 Version 22H2 for x64-based Systems | 10.0.22621.3447 · KB5036893 | Microsoft (MSRC) |
| Windows 11 Version 23H2 for ARM64-based Systems | 10.0.22631.3447 · KB5036893 | Microsoft (MSRC) |
| Windows 11 Version 23H2 for x64-based Systems | 10.0.22631.3447 · KB5036893 | Microsoft (MSRC) |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | 6.0.6003.22618 · KB5036932 | Microsoft (MSRC) |
| Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) | 6.0.6003.22618 · KB5036932 | Microsoft (MSRC) |
| Windows Server 2008 for x64-based Systems Service Pack 2 | 6.0.6003.22618 · KB5036932 | Microsoft (MSRC) |
| Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) | 6.0.6003.22618 · KB5036932 | Microsoft (MSRC) |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | 6.1.7601.27067 · KB5036967 | Microsoft (MSRC) |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | 6.1.7601.27067 · KB5036967 | Microsoft (MSRC) |
| Windows Server 2012 | 6.2.9200.24821 · KB5036969 | Microsoft (MSRC) |
| Windows Server 2012 (Server Core installation) | 6.2.9200.24821 · KB5036969 | Microsoft (MSRC) |
| Windows Server 2012 R2 | 6.3.9600.21924 · KB5036960 | Microsoft (MSRC) |
| Windows Server 2012 R2 (Server Core installation) | 6.3.9600.21924 · KB5036960 | Microsoft (MSRC) |
| Windows Server 2016 | 10.0.14393.6897 · KB5036899 | Microsoft (MSRC) |
+6
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-3806991 days apartWindows Enroll Engine Security Feature Bypass Vulnerability28Monitor
- CVE-2023-28228364 days apartWindows Spoofing Vulnerability22Monitor
- CVE-2023-28226364 days apartWindows Enroll Engine Security Feature Bypass Vulnerability21Monitor
- CVE-2025-55229499 days apartWindows Certificate Spoofing Vulnerability21Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
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
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.