dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-58716

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
Improper input validation 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

This vulnerability in Microsoft Windows Speech involves improper input validation that allows an authorized local attacker to escalate privileges to a higher integrity level. The issue stems from the Speech component not properly validating input before processing, which can be exploited to execute code with elevated permissions.

MitigationApply the Microsoft security update for CVE-2025-58716 when released, as this is a core Windows component vulnerability requiring vendor-supplied patches to remediate.

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 10 build version
    Open Command Prompt and run 'winver' to display the OS build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get detailed build information
    Affected if The build number is below 10.0.10240.21161 (1507), 10.0.14393.8519 (1607), 10.0.17763.7919 (1809), 10.0.19044.6456 (21h2), or 10.0.19045.6456 (22h2)
  2. Check Windows 11 build version
    Open Command Prompt and run 'winver' to display the OS build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get detailed build information
    Affected if The build number is below 10.0.22621.6060 (22h2), between 10.0.22631.0 and 10.0.22631.6060 (23h2), or below 10.0.26100.6899 (24h2)
  3. Identify exact Windows release version
    Run 'winver' and note the version listed (such as 'Version 22H2' or '23H2') to map the build number to the correct affected version range
    Affected if The identified release version corresponds to a build number that falls within any of the vulnerable ranges listed in the CVE
  4. Confirm Speech component presence
    Check if the Windows Speech recognition feature is installed by going to Settings > Time & Language > Speech, or by searching for 'Speech' in Windows Settings
    Affected if The Speech component is available on the system (this is a default component in most Windows editions, so most installations are potentially affected if the version is vulnerable)

A system is affected if it runs any Windows 10 or Windows 11 version with a build number lower than the safe thresholds specified for each release, and the Speech component is present (which is the default in most editions).

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 the Microsoft security update for CVE-2025-58716 when released, as this is a core Windows component vulnerability requiring vendor-supplied patches to remediate.

Recommended fix High confidence

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.22631.6070+ | Windows 11 24h2: 10.0.26100.6899+

  1. Open Settings > Update & Security > Windows Update and check for updates
  2. Install all available Windows security updates, which will include the fix for CVE-2025-58716
  3. Restart the system if prompted to complete the installation
  4. Verify the installation by checking Windows version: Win+R, type 'winver', and confirm the version meets or exceeds the fixed build number for your Windows release

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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