dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59195

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 or later.
See remediation →
72/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
Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Graphics Component 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 · low confidence

A race condition vulnerability in Microsoft Graphics Component allows an authorized local attacker to cause a denial of service by improperly synchronizing access to shared resources during concurrent execution.

MitigationApply Microsoft security updates for the Graphics Component when released; implement least-privilege access controls to limit local attackers.

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 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
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 2019Operating system
Affected:< 10.0.17763.7919

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

CVSS:3.1/AV:L/AC:H/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
    Run 'winver' from command prompt or check 'System Information' (msinfo32). Look for the OS Name and Version fields showing build number (e.g., 10.0.19045.6456)
    Affected if The displayed build number falls below the threshold for your Windows edition as listed in the affected versions
  2. Identify exact Windows edition
    Run 'systeminfo' or check 'winver' to determine if the system is Windows 10 1809, 21h2, 22h2, Windows 11 22h2, 23h2, 24h2, 25h2, or Windows Server 2019
    Affected if The edition matches any of the affected products listed in the CVE
  3. Compare build number against affected ranges
    Extract the full build number (e.g., 10.0.19045.XXXX) and compare: Windows 10 1809/Server 2019 requires < 10.0.17763.7919; Windows 10 21h2 requires < 10.0.19044.6456; Windows 10 22h2 requires < 10.0.19045.6456; Windows 11 22h2 requires < 10.0.22621.6060; Windows 11 23h2 requires <= 10.0.22631.6060; Windows 11 24h2 requires < 10.0.26100.6899; Windows 11 25h2 requires < 10.0.26200.6899
    Affected if The installed build number is lower than the specified threshold for the detected Windows edition and version
  4. Verify Graphics Component is present
    The vulnerability exists in Microsoft Graphics Component. On Windows systems with GUI (desktop experience), this component is present by default. Confirm the system has a graphical interface installed
    Affected if The system has a graphical desktop environment (most Windows desktop and server installations with Desktop Experience)
  5. Check for pending security updates
    Open Settings > Windows Update > Update History or run 'wmic qfe list' to see installed security updates. Look for updates related to the Graphics Component or this specific CVE
    Affected if No graphics-related security update matching this CVE has been installed (build remains at affected version)

The system is affected if it runs any of the listed Windows editions and its current build number is below the specified threshold for that edition, and the Graphics Component is present (standard on desktop Windows installations).

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.17763.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply Microsoft security updates for the Graphics Component when released; implement least-privilege access controls to limit local attackers.

Recommended fix High confidence

Install the corresponding Windows Security Update (KB) containing the fix for CVE-2025-59195 - specific KB numbers can be found in Microsoft Security Response Center advisories for this CVE

  1. 1. Verify current Windows build version by opening Settings > System > About or running 'winver' command
  2. 2. Check if your current build is lower than the fixed version for your Windows edition
  3. 3. Open Windows Update: Settings > Windows Update > Check for updates
  4. 4. Install all available security updates, particularly those marked for Microsoft Graphics Component
  5. 5. Restart the system when prompted to complete the update installation
  6. 6. After restart, verify the new build version matches or exceeds: 10.0.17763.7919 (Win10 1809/Server 2019), 10.0.19044.6456 (Win10 21h2), 10.0.19045.6456 (Win10 22h2), 10.0.22621.6060 (Win11 22h2), 10.0.22631.6061+ (Win11 23h2), 10.0.26100.6899 (Win11 24h2), or 10.0.26200.6899 (Win11 25h2)
Caveat Standard Windows update - no expected breaking changes for this security patch; always backup critical data before applying updates as a general precaution

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

Fix this in Windows 10 1809 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-2025-59195 — 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-59195 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