dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-48573

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
No cwe for this issue 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 in Windows Secure Boot. An authorized attacker with local access can bypass Secure Boot's security controls, potentially loading untrusted operating systems or bootloaders. Secure Boot is a UEFI firmware security feature that prevents unauthorized operating systems from loading during the startup process.

MitigationApply Microsoft security patches for Windows as they become available for this vulnerability. Verify Secure Boot is enabled and functioning correctly in UEFI settings, and ensure all firmware/BIOS updates are installed.

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. Identify your Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' to see the Windows version and build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get detailed version information.
    Affected if The build number displayed is lower than the threshold for your Windows release (10.0.14393.9234 for 1607, 10.0.17763.8880 for 1809, 10.0.19044.7417 for 21h2, 10.0.19045.7417 for 22h2, 10.0.22631.7219 for 23h2, 10.0.26100.8655 for 24h2, 10.0.26200.8655 for 25h2, or 10.0.28000.2269 for 26h1).
  2. Confirm the specific Windows release name
    Run 'winver' and note the release (such as 'Version 1607', 'Version 1809', 'Version 21H2', 'Version 22H2', or the Windows 11 release name like '23H2', '24H2', '25H2', '26H1') to match against the affected product list.
    Affected if Your Windows release matches one of the affected versions listed and the build number is below the corresponding threshold.
  3. Verify if Secure Boot is enabled
    Open PowerShell and run 'Confirm-SecureBootUEFI' to check the Secure Boot status, or access UEFI/BIOS settings during boot to view the Secure Boot configuration.
    Affected if Secure Boot is reported as 'True' or enabled, meaning your system is using the security feature that this vulnerability bypasses.
  4. Check Secure Boot configuration via BCDedit
    Run 'bcdedit /enum all' in Command Prompt and look for the 'secureboot' entry under the Windows Boot Loader or Firmware sections to confirm Secure Boot is active.
    Affected if The output shows 'secureboot' as enabled or 1, indicating the feature is turned on in the boot configuration.

You are affected if your Windows version and build fall within any of the listed version ranges AND Secure Boot is enabled in your system, as the bypass only impacts environments using Secure Boot protection.

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 patches for Windows as they become available for this vulnerability. Verify Secure Boot is enabled and functioning correctly in UEFI settings, and ensure all firmware/BIOS updates are installed.

Recommended fix High confidence

Apply Windows security updates to reach the minimum fixed build version for your specific Windows version as listed above (e.g., Windows 10 22h2: 10.0.19045.7417, Windows 11 24h2: 10.0.26100.8655)

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo'
  2. Determine which affected version category applies (Windows 10 version or Windows 11 version and build)
  3. Apply the appropriate Windows security update that includes the fix for this vulnerability
  4. For Windows 10 1607: upgrade to build 10.0.14393.9234 or later
  5. For Windows 10 1809: upgrade to build 10.0.17763.8880 or later
  6. For Windows 10 21h2: upgrade to build 10.0.19044.7417 or later
  7. For Windows 10 22h2: upgrade to build 10.0.19045.7417 or later
  8. For Windows 11 23h2: upgrade to build 10.0.22631.7219 or later
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for business-critical applications before deploying

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-48573 — 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-48573 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