dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-59508

HIGH · 7.0 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 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 Windows Speech 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

A race condition vulnerability exists in Windows Speech where improper synchronization of shared resources allows a local authorized attacker to exploit concurrent execution and elevate privileges to higher integrity levels.

MitigationApply Microsoft security updates for CVE-2025-59508 once released; restrict local machine access to trusted administrative users in the interim.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2016Operating system
Affected:< 10.0.14393.8594

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. Identify installed Windows version
    Run `winver` from command prompt or check System Properties, or run `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
    Affected if The displayed version falls below any of these thresholds: Windows 10 1607 < 10.0.14393.8594, Windows 10 1809 < 10.0.17763.8027, Windows 10 21h2 < 10.0.19044.6575, Windows 10 22h2 < 10.0.19045.6575, Windows 11 23h2 < 10.0.22631.6199, Windows 11 24h2 < 10.0.26100.7092, Windows 11 25h2 < 10.0.26200.70
  2. Determine Windows build number
    Run `winver` or `systeminfo` and note the full build number (e.g., 10.0.19045.xxxx)
    Affected if The build number is lower than the version thresholds listed in the affected products
  3. Confirm Windows Speech component availability
    Check if the Windows Speech service (SpeechRuntime) or related Speech user-mode components exist on the system; verify by searching for "speech" in installed Windows features or checking C:\Windows\Speech_OneCore for presence
    Affected if The Windows Speech component is present and accessible to the local user context, combined with a vulnerable version from step 1 or 2

You are affected if your Windows version build number is below any of the specified thresholds AND the Windows Speech component is present and accessible on your 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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply Microsoft security updates for CVE-2025-59508 once released; restrict local machine access to trusted administrative users in the interim.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8594 | Windows 10 1809: 10.0.17763.8027 | Windows 10 21h2: 10.0.19044.6575 | Windows 10 22h2: 10.0.19045.6575 | Windows 11 23h2: 10.0.22631.6199 | Windows 11 24h2: 10.0.26100.7092 | Windows 11 25h2: 10.0.26200.7092 | Windows Server 2016: 10.0.14393.8594

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 build is installed and match it to the affected version ranges listed in the CVE
  3. Apply the appropriate Microsoft security update for CVE-2025-59508 through Windows Update or by downloading from the Microsoft Update Catalog
  4. Restart the system after the update is installed
  5. Verify the update was successfully installed by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows security updates typically have minimal risk; test in non-production environment before broad deployment

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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