dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-59507

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 an authorized local attacker to elevate privileges. The vulnerability stems from concurrent execution issues in the Windows Speech component that can be exploited to gain higher-level access.

MitigationApply Microsoft security updates for Windows when available; ensure local user privileges are appropriately restricted and monitor for suspicious processes interacting with the Windows Speech service.

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. Check installed Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the installed Windows version and build number
    Affected if The version falls within any of these ranges: 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 S
  2. Verify Windows Speech component presence
    Check for the presence of sapi.dll or Speech-related files in C:\Windows\System32\Speech or verify via PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup' -ErrorAction SilentlyContinue
    Affected if The Windows Speech component files exist on the system (the vulnerability applies only when this component is present)
  3. Check Windows Speech service status
    Run 'Get-Service -Name *Speech*' or 'sc query speech' in an elevated command prompt to list any Windows Speech-related services
    Affected if A Windows Speech service is installed and running on the system

Your system is affected if it runs a Windows version listed as vulnerable AND has the Windows Speech component installed and active.

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 Windows when available; ensure local user privileges are appropriately restricted and monitor for suspicious processes interacting with the Windows Speech service.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.8594 or later | Windows 10 1809: build 10.0.17763.8027 or later | Windows 10 21h2: build 10.0.19044.6575 or later | Windows 10 22h2: build 10.0.19045.6575 or later | Windows 11 23h2: build 10.0.22631.6199 or later | Windows 11 24h2: build 10.0.26100.7092 or later |

  1. Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Determine which Windows version and build you are running from the list: Windows 10 1607 (build 14393), Windows 10 1809 (build 17763), Windows 10 21h2 (build 19044), Windows 10 22h2 (build 19045), Windows 11 23h2 (build 22631), Windows 11 24h2 (build 26100), Windows 11 25h2 (build 26200), or Windows Server 2016 (build 14393)
  3. Apply the appropriate Windows Security Update that addresses CVE-2025-59507. For most systems, this will be the May 2025 Windows Update or later security patch
  4. Verify the update was installed successfully by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
  5. Restart the system as required by the update installation
Caveat Standard Windows update apply with no expected breaking changes; patch is a security fix for local privilege escalation

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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