dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32153

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.17763.8644 / 10.0.19044.7184 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 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

A use-after-free vulnerability in Microsoft Windows Speech allows a local, authenticated attacker to potentially achieve arbitrary code execution with elevated privileges by exploiting memory that is accessed after being freed.

MitigationApply the Microsoft security update for CVE-2026-32153 when released, or implement least-privilege policies and restrict access to the Windows Speech service to mitigate local privilege escalation risk.

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.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 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The build number is lower than the threshold for your Windows version (17763.8644 for 1809, 19044.7184 for 21h2, 19045.7184 for 22h2, 22631.6936 for 23h2, 26100.8246 for 24h2, 26200.8246 for 25h2, or 28000.1836 for 26h1)
  2. Identify Windows edition
    Run 'winver' or check System Properties to confirm whether you are on Windows 10 or Windows 11, and which specific release (such as 1809, 21h2, 22h2, 23h2, 24h2, 25h2, or 26h1)
    Affected if You are on an affected release and your build falls below the corresponding threshold
  3. Check Windows Speech service status
    Run 'Get-Service -Name SpeechRuntimeService' in PowerShell, or check Services.msc for the Windows Speech service
    Affected if The Speech service is installed and running (vulnerability requires the Speech component to be active)
  4. Verify Speech Runtime is enabled
    Check Registry key 'HKLM\SOFTWARE\Microsoft\Speech\Server' or examine installed Windows Features for Speech recognition components
    Affected if Speech recognition or Speech synthesis features are enabled on the system

You are affected if your Windows build is lower than the version threshold for your specific Windows release AND the Windows Speech component is installed or running.

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.8644 / 10.0.19044.7184 / 10.0.19045.7184 or later
Fixed in 10.0.17763.864410.0.19044.718410.0.19045.7184
Interim mitigation

Apply the Microsoft security update for CVE-2026-32153 when released, or implement least-privilege policies and restrict access to the Windows Speech service to mitigate local privilege escalation risk.

Recommended fix High confidence

Install the Microsoft security update for CVE-2026-32153 to reach the fixed build version for your specific Windows edition

  1. Check current Windows version by running `winver` or `systeminfo` in Command Prompt
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates, specifically the Microsoft patch addressing CVE-2026-32153
  4. Restart the system when prompted
  5. Verify the fix by checking that the OS version matches or exceeds the fixed build number for your Windows version: Windows 10 1809 should be 10.0.17763.8644+, Windows 10 21H2 should be 10.0.19044.7184+, Windows 10 22H2 should be 10.0.19045.7184+, Windows 11 23H2 should be 10.0.22631.6936+, Windows 11 24H2 should be 10.0.26100.8246+, Windows 11 25H2 should be 10.0.26200.8246+, Windows 11 26H1 shoul
Caveat Standard Windows security update; no expected breaking changes for this privilege escalation patch

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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