dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-45600

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.26100.8655 / 10.0.26100.32995 or later.
See remediation →
80/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
Access of resource using incompatible type ('type confusion') in Windows Kernel-Mode Drivers allows an authorized attacker to elevate privileges 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

Type confusion vulnerability in Windows Kernel-Mode Drivers allows a locally authenticated attacker to manipulate driver behavior through incompatible type access, potentially escalating privileges to SYSTEM level.

MitigationApply Microsoft security updates immediately upon release; prioritize patching kernel-mode drivers on high-privilege systems. Monitor vendor advisories for specific affected drivers.

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 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
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 version against affected releases
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"Version"' and compare the build number to: Windows 11 24h2 (build < 26100.8655), 25h2 (build < 26200.8655), 26h1 (build < 28000.2269), or Windows Server 2025 (build < 26100.32995)
    Affected if The installed Windows build number falls below the fixed version numbers listed for any affected product
  2. Confirm kernel-mode drivers are loaded
    Run 'driverquery /v | findstr /i "Running"' or check Device Manager for loaded drivers. Kernel-mode drivers run at the highest privilege level.
    Affected if Kernel-mode drivers are present (standard on Windows, but necessary for the vulnerable code path to be reachable)
  3. Identify running kernel driver services
    Run 'sc query type= driver' or check registry at HKLM\SYSTEM\CurrentControlSet\Services for driver entries
    Affected if Any kernel-mode drivers are installed and running on the system

The system is potentially affected if it runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 with a build number below the specified thresholds, and has kernel-mode drivers loaded (which is the default configuration).

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.26100.8655 / 10.0.26100.32995 / 10.0.26200.8655 or later
Fixed in 10.0.26100.865510.0.26100.3299510.0.26200.8655
Interim mitigation

Apply Microsoft security updates immediately upon release; prioritize patching kernel-mode drivers on high-privilege systems. Monitor vendor advisories for specific affected drivers.

Recommended fix High confidence

Windows 11 24h2 build 10.0.26100.8655 or later | Windows 11 25h2 build 10.0.26200.8655 or later | Windows 11 26h1 build 10.0.28000.2269 or later | Windows Server 2025 build 10.0.26100.32995 or later

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update > Check for updates
  3. Install all available cumulative updates until the version reaches or exceeds the fixed build number for your product: Windows 11 24h2 requires 10.0.26100.8655 or later, Windows 11 25h2 requires 10.0.26200.8655 or later, Windows 11 26h1 requires 10.0.28000.2269 or later, Windows Server 2025 requires 10.0.26100.32995 or later
  4. Restart the system when prompted to complete the update installation
  5. Verify the installed version matches or exceeds the required fixed build number
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for critical systems before applying

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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