dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-55339

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.20348.4294 / 10.0.22621.6060 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
Out-of-bounds read in Windows NDIS 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

An out-of-bounds read vulnerability in Windows NDIS (Network Driver Interface Specification) allows a locally authorized attacker to read unintended kernel memory, which can be leveraged to elevate privileges to SYSTEM level.

MitigationApply the Microsoft security update for CVE-2025-55339 once released, as this kernel-level vulnerability requires a vendor-supplied patch to remediate.

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 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2022Operating system
Affected:< 10.0.20348.4294
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1913
Windows Server 2025Operating system
Affected:< 10.0.26100.6899

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 and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Alternatively, run 'ver' in cmd or '$PSVersionTable in PowerShell'
    Affected if The reported version/build falls below any of the following: Windows 11 22h2 < 10.0.22621.6060, 23h2 < 10.0.22631.6060, 24h2 < 10.0.26100.6899, 25h2 < 10.0.26200.6899, Server 2022 < 10.0.20348.4294, Server 2022 23h2 < 10.0.25398.1913, Server 2025 < 10.0.26100.6899
  2. Verify NDIS driver is present
    Open Device Manager, expand 'Network adapters', or run 'netsh interface show' in PowerShell to confirm network interfaces are active. NDIS is the underlying driver architecture for network adapters in Windows
    Affected if Any network adapter is present and enabled, as NDIS is the foundational layer for Windows networking and the vulnerability exists in the NDIS driver stack itself
  3. Confirm local authorization context
    Review system users and permissions using 'whoami /all' or check if the attacker has an existing local user account on the system
    Affected if The system allows local user accounts (standard non-admin accounts) or if untrusted users have any form of local access, as the CVEs description states it requires a locally authorized attacker

You are affected if your Windows version/build is below the thresholds listed and the system has any network adapters enabled (which is the default configuration), allowing a locally authenticated user to potentially exploit the NDIS out-of-bounds read for privilege escalation.

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.20348.4294 / 10.0.22621.6060 / 10.0.22631.6060 or later
Fixed in 10.0.20348.429410.0.22621.606010.0.22631.6060
Interim mitigation

Apply the Microsoft security update for CVE-2025-55339 once released, as this kernel-level vulnerability requires a vendor-supplied patch to remediate.

Recommended fix High confidence

Windows Security Update (specific build numbers per version - see steps)

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. 2. Determine which affected version category applies to your system (Windows 11 version, Windows Server version)
  3. 3. Apply the relevant Windows Security Update from Microsoft Update Catalog or via Windows Update
  4. 4. For Windows 11 22h2: Install update containing build 10.0.22621.6060 or later
  5. 5. For Windows 11 23h2: Install update containing build 10.0.22631.6060 or later
  6. 6. For Windows 11 24h2: Install update containing build 10.0.26100.6899 or later
  7. 7. For Windows 11 25h2: Install update containing build 10.0.26200.6899 or later
  8. 8. For Windows Server 2022: Install update containing build 10.0.20348.4294 or later
Caveat Standard Windows update risks apply - test in staging environment before production deployment

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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