dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54895

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 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
Integer overflow or wraparound in Windows SPNEGO Extended Negotiation 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

This is a local privilege escalation vulnerability in Windows SPNEGO (Simple and Protected GSS-API Negotiation Mechanism) Extended Negotiation. An integer overflow or wraparound flaw in the authentication negotiation process allows an authorized attacker to gain elevated privileges on the local system.

MitigationApply the relevant Microsoft security updates for Windows SPNEGO component. Prioritize patching domain controllers and systems handling sensitive authentication operations, as SPNEGO is critical to Windows authentication workflows.

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 1507Operating system
Affected:< 10.0.10240.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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"' to obtain the exact build number
    Affected if The build number falls below the thresholds: 10240.21128 (1507), 14393.8422 (1607), 17763.7792 (1809), 19044.6332 (21h2), 19045.6332 (22h2), 22621.5909 (11 22h2), 22631.5909 (11 23h2), 26100.6508 (11 24h2)
  2. Confirm SPNEGO is in use
    SPNEGO (Simple and Protected GSS-API Negotiation Mechanism) is used by default for Windows authentication. Check for presence of Kerberos or NTLM authentication by examining event logs under Security or by checking that the system participates in domain authentication
    Affected if The system runs any version of Windows 10 or Windows 11 that matches the affected build ranges and utilizes SPNEGO for authentication negotiation

A system is affected if it runs a Windows 10 or 11 version with a build number lower than the specified thresholds AND utilizes SPNEGO-based authentication, which is the default for Windows domain authentication workflows.

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.10240.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply the relevant Microsoft security updates for Windows SPNEGO component. Prioritize patching domain controllers and systems handling sensitive authentication operations, as SPNEGO is critical to Windows authentication workflows.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21128 | Windows 10 1607: 10.0.14393.8422 | Windows 10 1809: 10.0.17763.7792 | Windows 10 21h2: 10.0.19044.6332 | Windows 10 22h2: 10.0.19045.6332 | Windows 11 22h2: 10.0.22621.5909 | Windows 11 23h2: 10.0.22631.5909 | Windows 11 24h2: 10.0.26100.6508

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Settings > Windows Update (or run 'ms-settings:windowsupdate')
  3. Click 'Check for updates' and install all available security updates
  4. If the specific KB is not offered, download the security update from the Microsoft Update Catalog (search for the CVE number)
  5. Restart the computer after the update completes
  6. Verify the installed build matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply: possible compatibility issues with legacy software, requires restart

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

Fix this in Windows 10 1507 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-2025-54895 — 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-54895 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