dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-48568

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 or security feature bypass vulnerability in Windows Secure Boot. An authorized attacker with local access can circumvent Secure Boot's protection mechanism, potentially allowing execution of untrusted code during the boot process. The vulnerability likely involves a flaw in how Windows validates Secure Boot components or configurations.

MitigationApply Microsoft security patches for Windows Secure Boot vulnerabilities and ensure UEFI firmware is updated to the latest manufacturer version. Verify Secure Boot is properly enabled and functioning in the system BIOS/UEFI 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. Identify installed Windows version
    Open Settings > System > About, or run 'winver' command, or run 'systeminfo' in Command Prompt and look at the OS Version line
    Affected if The installed version falls outside the patched version ranges: Windows 10 1607 (>=10.0.14393.9234), 1809 (>=10.0.17763.8880), 21h2 (>=10.0.19044.7417), 22h2 (>=10.0.19045.7417); Windows 11 23h2 (>=10.0.22631.7219), 24h2 (>=10.0.26100.8655), 25h2 (>=10.0.26200.8655), 26h1 (>=10.0.28000.2269)
  2. Verify Secure Boot status is enabled
    Run 'Confirm-SecureBootUEFI' in PowerShell; returns True if enabled, False if disabled or not supported
    Affected if Secure Boot returns True (enabled), because this vulnerability is a bypass of Secure Boot protection mechanisms
  3. Check Secure Boot configuration via msinfo32
    Open msinfo32 and look at the 'Secure Boot State' value in the BIOS/UEFI information section
    Affected if Secure Boot State shows as 'Enabled' indicating the feature is active and could potentially be bypassed
  4. Verify UEFI firmware version
    Access UEFI/BIOS setup during boot, or run 'fwupdmgr get-devices' on systems with firmware update tools, or check manufacturer documentation for current UEFI version
    Affected if UEFI firmware is outdated (manufacturer has not released updates), which may leave the underlying boot chain vulnerable alongside the Windows component flaw

A system is affected if it runs a Windows version below the patched thresholds listed above AND has Secure Boot enabled in UEFI settings.

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 Secure Boot vulnerabilities and ensure UEFI firmware is updated to the latest manufacturer version. Verify Secure Boot is properly enabled and functioning in the system BIOS/UEFI settings.

Recommended fix High confidence

Apply Windows Security Update KB for CVE-2026-48568 (check MSRC for specific KB number)

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually install the specific KB patch from Microsoft Update Catalog corresponding to your Windows version
  5. Verify the installation succeeded by checking that the build number matches or exceeds: 10.0.14393.9234 (Win10 1607), 10.0.17763.8880 (Win10 1809), 10.0.19044.7417 (Win10 21h2), 10.0.19045.7417 (Win10 22h2), 10.0.22631.7219 (Win11 23h2), 10.0.26100.8655 (Win11 24h2), 10.0.26200.8655 (Win11 25h2), or 10.0.28000.2269 (Win11 26h1)
  6. Restart the system to ensure Secure Boot updates take effect

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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