dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2025-62463

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.19044.6691 / 10.0.19045.6691 or later.
See remediation →
67/100
Remediation priority · Elevated
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 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

A null pointer dereference vulnerability exists in Windows DirectX graphics subsystem. When an authorized local attacker triggers specific conditions in DirectX components, the application attempts to dereference a null pointer, causing a crash and resulting in local denial of service.

MitigationApply the appropriate Microsoft security update for Windows DirectX when released. Test the patch in a non-production environment to ensure compatibility with graphics-dependent applications.

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 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2022Operating system
Affected:< 10.0.20348.4467
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.2025
Windows Server 2025Operating system
Affected:< 10.0.26100.7392

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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 version and build number
    Run 'winver' from command prompt or 'systeminfo' and note the OS Build number shown (for example 19045.6691)
    Affected if The build number is lower than the threshold for your Windows version (10.0.19044.6691 for 21h2, 10.0.19045.6691 for 22h2, 10.0.22631.6345 for 11 23h2, 10.0.26100.7392 for 11 24h2, 10.0.26200.7392 for 11 25h2, 10.0.20348.4467 for Server 2022, 10.0.25398.2025 for Server 2022 23h2, or 10.0.26100.7392
  2. Confirm Windows edition matches affected product list
    Run 'winver' or check System Properties to verify the exact Windows edition (Home, Pro, Enterprise, Server, etc.)
    Affected if The edition is one of the affected products listed (Windows 10 21h2, 10 22h2, 11 23h2, 11 24h2, 11 25h2, Server 2022, Server 2022 23h2, or Server 2025)
  3. Verify DirectX is available on the system
    Run 'dxdiag' from command prompt and check if DirectX Diagnostic Tool launches successfully
    Affected if DirectX is functional on the system (this is the default for desktop Windows editions; for Server editions, Desktop Experience feature must be installed)

You are affected if your Windows build number falls below the threshold for your specific Windows edition and DirectX is present and functional on the system.

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.19044.6691 / 10.0.19045.6691 / 10.0.20348.4467 or later
Fixed in 10.0.19044.669110.0.19045.669110.0.20348.4467
Interim mitigation

Apply the appropriate Microsoft security update for Windows DirectX when released. Test the patch in a non-production environment to ensure compatibility with graphics-dependent applications.

Recommended fix High confidence

Windows 10 21h2: build 10.0.19044.6691 | Windows 10 22h2: build 10.0.19045.6691 | Windows 11 23h2: build 10.0.22631.6345 | Windows 11 24h2: build 10.0.26100.7392 | Windows 11 25h2: build 10.0.26200.7392 | Windows Server 2022: build 10.0.20348.4467 | Windows Server 2022 23h2: build 10.0.25398.2025 |

  1. Identify the current Windows version by running 'winver' or 'systeminfo'
  2. Determine the applicable Windows release (21h2, 22h2, 23h2, 24h2, 25h2 for client; 2022, 2022 23h2, 2025 for Server)
  3. Open Settings > Windows Update and check for updates, or use Windows Server Update Services (WSUS) for enterprise environments
  4. Install the cumulative update that includes the security fix for CVE-2025-62463
  5. Verify the installed version matches or exceeds the fixed build number for your release
  6. Restart the system if prompted to complete the update installation
Caveat Standard Windows cumulative update apply with no special breaking changes expected; as a denial-of-service vulnerability fix, this update is routine and low-risk

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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