dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32089

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
80/100
Remediation priority · High
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
Use after free in Windows Speech Brokered Api 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 use-after-free vulnerability in the Windows Speech Brokered API allows a locally authorized attacker to exploit memory corruption and elevate privileges to higher integrity levels on the affected system.

MitigationApply Microsoft security updates for this vulnerability (once available) to all affected Windows systems. If the Speech Brokered API is not required, consider disabling the Windows Speech service as a defense-in-depth measure.

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.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

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

CVSS:3.1/AV:L/AC:L/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 Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows build number, then compare against the listed version thresholds: Windows 10 1607 < 10.0.14393.9060, 1809 < 10.0.17763.8644, 21h2 < 10.0.19044.7184, 22h2 < 10.0.19045.7184; Windows 11 23h2 < 10.0.22631.6936, 24h2 < 10.0.26100.8246, 25h2 < 10.0.26200.8246, 26h1 < 10.0.28000.1836
    Affected if The installed Windows build number falls below the threshold for the corresponding version branch
  2. Verify Windows Speech service status
    Open Services (services.msc) and locate the 'Windows Speech' service or check via PowerShell: 'Get-Service -Name "Speech*"' to enumerate speech-related services
    Affected if The Windows Speech service is installed and running on the system
  3. Confirm Speech Brokered API availability
    Check for the presence of speech broker components by examining: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Brokered in the registry, or look for sapi.dll and related speech runtime files in System32
    Affected if The Speech Brokered API components are registered and accessible on the system

A system is affected if it runs a Windows version below the specified build thresholds AND has the Windows Speech service or Speech Brokered API components enabled.

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.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply Microsoft security updates for this vulnerability (once available) to all affected Windows systems. If the Speech Brokered API is not required, consider disabling the Windows Speech service as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to the fixed build for your Windows version: Windows 10 1607 to build 10.0.14393.9060, Windows 10 1809 to build 10.0.17763.8644, Windows 10 21h2 to build 10.0.19044.7184, Windows 10 22h2 to build 10.0.19045.7184, Windows 11 23h2 to build 10.0.22631.6936, Windows 11 24h2 to build 10.0.26100.8

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or Windows 11 version and build is installed
  3. 3. Navigate to Windows Update: Settings > Update & Security > Windows Update
  4. 4. Check for updates and install all available security updates
  5. 5. Alternatively, manually download the specific security update for your Windows version from the Microsoft Update Catalog (catalog.update.microsoft.com)
  6. 6. After installation, restart the system to apply the changes
  7. 7. Verify the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update process with no expected breaking changes; this is a security patch

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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