dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-55698

HIGH · 7.7 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.26100.6899 / 10.0.26200.6899 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
Null pointer dereference in Windows DirectX allows an authorized attacker to deny service over a network.

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

A null pointer dereference vulnerability exists in Windows DirectX that can be triggered by an authorized attacker over the network, causing the affected system to crash or become unresponsive, resulting in denial of service.

MitigationApply vendor-supplied Microsoft security patches for Windows DirectX when available. Until then, restrict network access to affected systems and limit authorization scope to minimize attack surface.

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.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if Build number is below 10.0.26100.6899 for Windows 11 24h2 or Server 2025, or below 10.0.26200.6899 for Windows 11 25h2
  2. Confirm Windows edition
    Run 'systeminfo' and check the 'OS Name' field to identify if the system is Windows 11 24h2, Windows 11 25h2, or Windows Server 2025
    Affected if The edition matches one of the affected products and the build version falls within the affected range
  3. Verify DirectX is present
    Run 'dxdiag' and check the DirectX Version field; DirectX is integrated into Windows but this confirms the component is available
    Affected if DirectX is installed (which is default on affected Windows editions) - the vulnerability applies when DirectX is present on an affected build
  4. Check for network services using DirectX
    Review running services and open network ports using 'netstat -an' - the CVE states the attack is network-based and targets an authorized attacker
    Affected if Network services that utilize DirectX components are exposed, increasing the attack surface for this vulnerability

A system is affected if it runs Windows 11 24h2, Windows 11 25h2, or Windows Server 2025 with a build number lower than the specified thresholds (10.0.26100.6899 or 10.0.26200.6899 depending on version) and has DirectX enabled, 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.6899 / 10.0.26200.6899 or later
Fixed in 10.0.26100.689910.0.26200.6899
Interim mitigation

Apply vendor-supplied Microsoft security patches for Windows DirectX when available. Until then, restrict network access to affected systems and limit authorization scope to minimize attack surface.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.6899 or later | Windows 11 25h2: build 10.0.26200.6899 or later | Windows Server 2025: build later than 10.0.26100.6899

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Windows Update (or Check for Updates in Control Panel)
  3. Click 'Check for updates' and wait for the process to complete
  4. Look for security updates related to DirectX or CVE-2025-55698
  5. Install any available updates that address this vulnerability
  6. Restart the computer when prompted to complete the installation
  7. Verify the installed build version matches or exceeds 10.0.26100.6899 for Windows 11 24h2/Windows Server 2025, or 10.0.26200.6899 for Windows 11 25h2

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
  • 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-2025-55698 — 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-55698 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