dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-58715

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Integer overflow or wraparound in Microsoft 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

Integer overflow in Microsoft Windows Speech component allows a local authorized attacker to elevate privileges. The vulnerability stems from improper integer handling in the speech processing functionality, which when exploited can lead to arbitrary code execution at a higher privilege level.

MitigationApply Microsoft security updates for CVE-2025-58715 when released. Prioritize patching workstations and servers with Windows Speech component enabled.

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 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
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

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 against affected ranges
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the installed Windows version and build number
    Affected if The installed version is below any of the following thresholds: Windows 10 1507 < 10.0.10240.21161, Windows 10 1607 < 10.0.14393.8519, Windows 10 1809 < 10.0.17763.7919, Windows 10 21h2 < 10.0.19044.6456, Windows 10 22h2 < 10.0.19045.6456, Windows 11 22h2 < 10.0.22621.6060, Windows 11 23h2 <= 10.0.2
  2. Confirm Windows Speech component is present
    Check for the presence of speech-related services and components. Run 'Get-Service -Name *Speech*' in PowerShell or check for the 'SpeechRuntime.exe' process. Also verify the presence of the Windows Speech Recognition feature under Control Panel > Programs > Programs and Features > Turn Windows features on or off
    Affected if The Windows Speech component or Windows Speech Recognition feature is installed and enabled on the system
  3. Identify if the system is a vulnerable workstation or server
    Review installed roles and features using 'Get-WindowsOptionalFeature -Online | Where-Object {$_.State -eq "Enabled" -and $_.FeatureName -like "*Speech*"}' in PowerShell. Check if the Speech service runs with elevated privileges
    Affected if The Speech component is running as a service on the system and the OS version matches the affected ranges in step 1

A system is affected if it runs any Windows 10 or 11 version within the affected ranges AND has the Windows Speech component enabled, since the vulnerability requires the speech processing functionality to be present.

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.10240.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply Microsoft security updates for CVE-2025-58715 when released. Prioritize patching workstations and servers with Windows Speech component enabled.

Recommended fix High confidence

Upgrade to a Windows build at or above: 10.0.10240.21161 (Win10 1507), 10.0.14393.8519 (Win10 1607), 10.0.17763.7919 (Win10 1809), 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)

  1. Press Win+R, type 'winver', and press Enter to check the current Windows version and build number
  2. Identify the Windows version and compare its build number against the fixed versions: 10.0.10240.21161 (1507), 10.0.14393.8519 (1607), 10.0.17763.7919 (1809), 10.0.19044.6456 (21h2), 10.0.19045.6456 (22h2), 10.0.22621.6060 (11 22h2), 10.0.22631.6060 (11 23h2), 10.0.26100.6899 (11 24h2)
  3. If the current build is lower than the fixed version for your Windows release, open Settings > Windows Update and check for updates
  4. Install all available security updates, or manually download and install the appropriate cumulative update from the Microsoft Update Catalog for your specific Windows version
  5. Restart the computer after the update installation
  6. Verify the installed build number matches or exceeds the fixed version for your Windows release using winver
Caveat Standard Windows update risks apply; ensure backups and compatibility testing for critical systems before deploying

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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