dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26240

HIGH · 8.0 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.10240.20596 / 10.0.14393.6897 or later.
See remediation →
83/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Secure Boot Security Feature Bypass Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Secure Boot bypass vulnerability in UEFI firmware. Secure Boot is a security standard that ensures only cryptographically trusted software runs during the system boot process. A successful bypass would allow an attacker to execute arbitrary untrusted code at boot time, potentially compromising the entire system chain of trust.

MitigationApply vendor-supplied firmware updates that address this vulnerability. Ensure Secure Boot is properly enabled and configured, and update the UEFI revocation database (dbx) if the update includes new revoked signatures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20596
Windows 10 1607Operating system
Affected:< 10.0.14393.6897
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to see the installed Windows build number
    Affected if The build number is lower than the threshold for your Windows version (e.g., for Windows 10 22h2, below 10.0.19045.4291)
  2. Confirm Windows edition and servicing history
    Run 'systeminfo' and note the OS Name, Version, and Build number. Verify which Windows 10/11 release (1507, 1607, 1809, 21h2, 22h2, or 23h2) is installed
    Affected if The build version corresponds to an affected release listed in the CVE and is below the fixed version threshold
  3. Verify Secure Boot status
    Open msinfo32 and look for 'Secure Boot State' or run 'Confirm-SecureBootUEFI' in PowerShell
    Affected if Secure Boot is enabled - the bypass only affects systems where Secure Boot is configured, as it circumvents the Secure Boot trust model
  4. Check UEFI firmware version
    Run 'Get-WmiObject win32_bios' in PowerShell or check firmware version through 'msinfo32' under 'BIOS Version'
    Affected if Firmware version cannot be directly compared against CVE thresholds as updates are vendor-specific; the vulnerability exists in the UEFI implementation, not in Windows itself

You are likely affected if you are running any of the listed Windows 10/11 versions below the fixed build thresholds AND have Secure Boot enabled in your system firmware.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20596 / 10.0.14393.6897 / 10.0.17763.5696 or later
Fixed in 10.0.10240.2059610.0.14393.689710.0.17763.5696
Interim mitigation

Apply vendor-supplied firmware updates that address this vulnerability. Ensure Secure Boot is properly enabled and configured, and update the UEFI revocation database (dbx) if the update includes new revoked signatures.

Recommended fix High confidence

Minimum fixed versions: Windows 10 1507: 10.0.10240.20596 | Windows 10 1607: 10.0.14393.6897 | Windows 10 1809: 10.0.17763.5696 | Windows 10 21h2: 10.0.19044.4291 | Windows 10 22h2: 10.0.19045.4291 | Windows 11 21h2: 10.0.22000.2899 | Windows 11 22h2: 10.0.22621.3447 | Windows 11 23h2: 10.0.22631.34

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 release channel (1507, 1607, 1809, 21h2, 22h2, 11 21h2, 11 22h2, or 11 23h2) is currently installed
  3. For Windows 10 1507: Upgrade to version 10.0.10240.20596 or later
  4. For Windows 10 1607: Upgrade to version 10.0.14393.6897 or later
  5. For Windows 10 1809: Upgrade to version 10.0.17763.5696 or later
  6. For Windows 10 21h2: Upgrade to version 10.0.19044.4291 or later
  7. For Windows 10 22h2: Upgrade to version 10.0.19045.4291 or later
  8. For Windows 11 21h2: Upgrade to version 10.0.22000.2899 or later
Caveat Security-only update with no expected breaking changes; standard Windows update compatibility applies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26240 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26240 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data