dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59509

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.17763.8027 / 10.0.19044.6575 or later.
See remediation →
57/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
Insertion of sensitive information into sent data in Windows Speech allows an authorized attacker to disclose information 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

Windows Speech feature inadvertently includes sensitive information in data transmissions, enabling a local authenticated attacker to access this information. The vulnerability stems from improper data handling within the Windows Speech component, where sensitive content gets appended to outbound communications.

MitigationApply Microsoft security updates for Windows when released. Until then, restrict local access to trusted users only and monitor system processes related to speech services.

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 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 2019Operating system
Affected:< 10.0.17763.8027
Windows Server 2022Operating system
Affected:< 10.0.20348.4346

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the installed Windows version number, then compare it to the affected version thresholds: 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 2019 (10.0.17763.8027), Windows Server 2022 (10.0.20348.4346)
    Affected if The installed version is lower than the corresponding threshold for your Windows release
  2. Verify if Windows Speech service is enabled
    Open Services console (services.msc) and locate 'Windows Speech' or related speech services, or run 'Get-Service *Speech*' in PowerShell to list speech-related services
    Affected if Windows Speech or Speech Runtime service is installed and running on the system
  3. Identify speech-related processes with network activity
    Open Task Manager, go to the Network tab, or use 'netstat -ano' to identify processes using network connections; cross-reference with known Windows speech processes such as SpeechRuntime.exe, SpeechSvc.exe, or related components in the Windows Speech folder
    Affected if Any Windows speech component process is establishing outbound network connections
  4. Review outbound data from speech services
    Use Windows Firewall logging or network capture tools to inspect outbound traffic originating from speech service processes, looking for unexpected data payloads that may contain sensitive information
    Affected if Speech service processes are transmitting data externally and the Windows version is below the fixed release

You are affected if your Windows version falls below the specified thresholds AND the Windows Speech feature is enabled and actively transmitting data over the network.

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.17763.8027 / 10.0.19044.6575 / 10.0.19045.6575 or later
Fixed in 10.0.17763.802710.0.19044.657510.0.19045.6575
Interim mitigation

Apply Microsoft security updates for Windows when released. Until then, restrict local access to trusted users only and monitor system processes related to speech services.

Recommended fix High confidence

Install the corresponding Microsoft security update (KB) for your Windows version - fixed builds are: 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.

  1. Open Windows Update and check for updates
  2. Install the latest cumulative security update for your Windows version
  3. Restart the system if prompted after update installation
  4. Verify the installed build number matches or exceeds the fixed version for your product

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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