dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-45588

HIGH · 7.9 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 or later.
See remediation →
81/100
Remediation priority · High
Zero-click

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
Protection mechanism failure in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.

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 local privilege escalation/bypass vulnerability affecting Windows Secure Boot's protection mechanisms. An authorized attacker with local access can bypass a security feature through a protection mechanism failure in the Secure Boot chain. The vulnerability enables circumventing Secure Boot controls designed to ensure only trusted operating system loaders execute during the boot process.

MitigationApply Microsoft security updates immediately when available. Organizations should review Secure Boot policies, ensure firmware is up to date, and consider additional monitoring of boot integrity. In enterprise environments, verify that BitLocker or other full-disk encryption is enabled as a compensating control.

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 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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 version against affected ranges
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to see the installed Windows version
    Affected if The version is below 10.0.14393.9234 (Win 10 1607), 10.0.17763.8880 (Win 10 1809), 10.0.19044.7417 (Win 10 21h2), 10.0.19045.7417 (Win 10 22h2), 10.0.22631.7219 (Win 11 23h2), 10.0.26100.8655 (Win 11 24h2), 10.0.26200.8655 (Win 11 25h2), or 10.0.28000.2269 (Win 11 26h1)
  2. Verify Secure Boot status
    Open PowerShell and run 'Confirm-SecureBootUEFI' - returns True if enabled, False if disabled, or may require admin rights on some systems
    Affected if Secure Boot is reported as enabled (True) - the vulnerability bypasses Secure Boot controls, so systems with Secure Boot disabled are not affected by this specific flaw
  3. Check UEFI firmware version
    Access UEFI/BIOS settings during boot (typically via F2, F10, F12, or Del key depending on manufacturer) and note the firmware version, or use 'firmwaremgr /list' from an elevated command prompt if available
    Affected if UEFI firmware is outdated and not patched for this Secure Boot bypass vulnerability - compare against any available firmware release notes from the system manufacturer

A system is affected if it runs a Windows version below the specified thresholds AND has Secure Boot enabled, allowing an attacker with local access to circumvent Secure Boot protections.

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.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply Microsoft security updates immediately when available. Organizations should review Secure Boot policies, ensure firmware is up to date, and consider additional monitoring of boot integrity. In enterprise environments, verify that BitLocker or other full-disk encryption is enabled as a compensating control.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9234 or later | Windows 10 1809: build 10.0.17763.8880 or later | Windows 10 21h2: build 10.0.19044.7417 or later | Windows 10 22h2: build 10.0.19045.7417 or later | Windows 11 23h2: build 10.0.22631.7219 or later | Windows 11 24h2: build 10.0.26100.8655 or later |

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine the specific build number from the affected list that applies to your Windows version
  3. Apply the latest Windows Security Update that includes the fix for CVE-2026-45588
  4. After update installation, verify the new build number meets or exceeds the minimum fixed version for your Windows release
  5. Confirm Secure Boot remains enabled in UEFI/BIOS settings post-update
  6. Restart the system to complete the update process
Caveat Standard Windows update apply risks (potential for update conflicts on heavily customized systems); ensure backup of critical data before applying updates

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation16.0 h
  • Implementation8.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45588 — 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-2026-45588 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