dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-47656

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 Boot Manager 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

A protection mechanism failure in Windows Boot Manager allows a locally authorized attacker to bypass a security feature. This is a security bypass vulnerability in the boot process that undermines a protection mechanism, potentially allowing an attacker to circumvent boot-time security controls.

MitigationApply Microsoft security updates for Windows Boot Manager when available, and verify that the affected security feature is properly enforced through boot manager configuration settings.

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 and build number
    Open Command Prompt and run `winver` or `systeminfo | findstr /B /C:"OS Version"`. Alternatively, press Win+R, type `winver`, and note the full version string (for example: "Version 23H2 (Build 22631.7195)").
    Affected if The displayed build number falls below the fixed version for your Windows release (see step 2).
  2. Identify exact Windows release version
    Run `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "DisplayVersion"` to get the release name (such as 21h2, 22h2, 23h2) and `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "CurrentBuild"` to get the numeric build.
    Affected if Unable to determine the exact release version for proper comparison.
  3. Compare against affected version ranges
    Match your release and build to the list: Windows 10 1607 needs <10.0.14393.9234; 1809 needs <10.0.17763.8880; 21h2 needs <10.0.19044.7417; 22h2 needs <10.0.19045.7417; 11 23h2 needs <10.0.22631.7219; 11 24h2 needs <10.0.26100.8655; 11 25h2 needs <10.0.26200.8655; 11 26h1 needs <10.0.28000.2269. Check your build against the threshold for your specific release.
    Affected if Your installed build number is lower than the threshold for your Windows release.
  4. Confirm Boot Manager component is in use
    Boot into the affected Windows installation. The vulnerability affects the Windows Boot Manager component used during system startup. If the system uses a third-party bootloader or has Secure Boot fully enforced with no legacy boot options, the attack surface may differ.
    Affected if The system uses Windows Boot Manager as the default bootloader and your version is vulnerable.

You are affected if your Windows installation matches one of the listed releases and the installed build number is lower than the specified threshold for that release.

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 for Windows Boot Manager when available, and verify that the affected security feature is properly enforced through boot manager configuration settings.

Recommended fix High confidence

Install the latest Windows security update from Windows Update or Microsoft Update Catalog for your specific Windows version

  1. Open Windows Settings and navigate to Windows Update
  2. Check for and install all available Windows security updates
  3. Verify the update installed successfully by checking the installed build number matches or exceeds: Windows 10 1607: 10.0.14393.9234 | Windows 10 1809: 10.0.17763.8880 | Windows 10 21h2: 10.0.19044.7417 | Windows 10 22h2: 10.0.19045.7417 | Windows 11 23h2: 10.0.22631.7219 | Windows 11 24h2: 10.0.26100.8655 | Windows 11 25h2: 10.0.26200.8655 | Windows 11 26h1: 10.0.28000.2269
  4. Restart the system to ensure the Boot Manager update is fully applied
  5. Confirm the protection mechanism is functioning by verifying Secure Boot remains enabled in UEFI/BIOS settings
Caveat Standard Windows update with no expected breaking changes; as a precaution, verify critical applications and boot configurations work post-update

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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