Windows 10 1809Operating system · Microsoft

CVE-2025-54919

HIGH · 7.5 CVSS v3.1 Published 2025-09-09

Fix available

A fix is available. Upgrade to 10.0.17763.7792 / 10.0.19044.6332 or later.

See remediation →

75/100

Remediation priority · High

Official description

NVD · unedited

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Win32K - GRFX allows an authorized attacker to execute code locally.

Technical summary

dbcve analysis · moderate confidence

A race condition vulnerability exists in the Windows Win32K kernel-mode graphics subsystem (GRFX) where concurrent execution with improper synchronization on shared resources allows a local authorized attacker to execute arbitrary code. The flaw stems from insufficient synchronization mechanisms in the graphics rendering path that can be exploited through carefully timed operations.

MitigationApply Microsoft security updates for CVE-2025-54919 via Windows Update or enterprise patch management systems. Prioritize patching given the local code execution capability and kernel-level access potential.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

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

Windows Server 2019Operating system

Affected:< 10.0.17763.7792

Windows Server 2022Operating system

Affected:< 10.0.20348.4106

CVSS breakdown

From the vector

Attack vector: Local
Complexity: High
Privileges: Low
User interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Retrieve 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 `winmgmt /exec /nosystemquery Win32_OperatingSystem` or check Settings > System > About.

Affected if The displayed build number falls below the fixed versions for your Windows release.
Identify Windows release version

Note whether your system is Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 22h2, Windows 11 23h2, Windows 11 24h2, Windows Server 2019, or Windows Server 2022. This determines which fixed build applies.

Affected if You are running any of the listed Windows 10 or Windows 11 releases, or Windows Server 2019/2022.
Compare build against fixed versions for your release

Match your detected build number to the appropriate threshold: Windows 10 1809/Server 2019: 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; Windows Server 2022: 10.0.20348.4106.

Affected if Your installed build number is LOWER than the corresponding fixed build for your Windows release.
Confirm Win32K graphics subsystem is in use

This vulnerability exists in the Win32K kernel-mode graphics subsystem (win32k.sys). On standard Windows desktop or server systems with graphics capabilities, this component is loaded by default. No specific feature check is needed as this is a kernel component active on graphical Windows installations.

Affected if The system runs a graphical Windows edition (desktop or server with GUI) - the Win32K subsystem is present and vulnerable if version criteria are met.

If your Windows build number is lower than the specified fixed build for your Windows release, your system is affected by this race condition in the Win32K graphics subsystem.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 10.0.17763.7792 / 10.0.19044.6332 / 10.0.19045.6332 or later

Fixed in 10.0.17763.779210.0.19044.633210.0.19045.6332

Interim mitigation

Apply Microsoft security updates for CVE-2025-54919 via Windows Update or enterprise patch management systems. Prioritize patching given the local code execution capability and kernel-level access potential.

Recommended fix High confidence

Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
Open Windows Update by navigating to Settings > Update & Security > Windows Update
Click 'Check for updates' to download and install the latest cumulative update
Ensure the installed build number meets or exceeds the fixed version for your Windows edition: Windows 10 1809/Server 2019 requires build 10.0.17763.7792, Windows 10 21h2 requires build 10.0.19044.6332, Windows 10 22h2 requires build 10.0.19045.6332, Windows 11 22h2 requires build 10.0.22621.5909, Windows 11 23h2 requires build 10.0.22631.5909, Windows 11 24h2 requires build 10.0.26100.6508, Windo
Restart the system after the update is installed

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

Fix this in Windows 10 1809 Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

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,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

msrc.microsoft.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54919 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-54919?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 10.0.17763.7792 / 10.0.19044.6332 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Windows 10 1809

Remediation

A high-priority fix

Fix this in Windows 10 1809 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-54919 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References