dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32090

HIGH · 7.0 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 →
72/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
Concurrent execution using shared resource with improper synchronization ('race condition') 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

This is a race condition vulnerability in Windows Speech Brokered API where improper synchronization during concurrent execution of shared resources allows a locally authorized attacker to elevate privileges. The vulnerability stems from timing-sensitive access to shared state without proper locking mechanisms.

MitigationApply the relevant Microsoft security update for this vulnerability once released. Until then, restrict local access to trusted users and monitor for unusual process behavior.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The displayed build number is lower than any of the following: 14393.9060 (Windows 10 1607), 17763.8644 (Windows 10 1809), 19044.7184 (Windows 10 21h2/22h2), 22631.6936 (Windows 11 23h2), 26100.8246 (Windows 11 24h2/25h2), or 28000.1836 (Windows 11 26h1)
  2. Confirm Windows edition and build string
    Run 'ver' in Command Prompt to get the version string in format like '10.0.XXXXX.xxxxx' or check Registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' for 'CurrentBuild' and 'DisplayVersion'
    Affected if The build number (CurrentBuild value) is below the affected thresholds listed in step 1
  3. Identify if Speech Brokered API component exists
    Check for the presence of the Speech Brokered API component by examining 'C:\Windows\System32\Speech\' directory or running 'Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Speech\' in PowerShell if the registry key exists
    Affected if The vulnerable component exists on the system (the race condition can only trigger if this Windows feature is present)
  4. Verify current patch level
    Run 'powershell "(Get-HotFix | Where-Object {$_.Description -eq 'Security Update' -or $_.Description -eq 'Update'} | Sort-Object -Property InstalledOn -Descending | Select-Object -First 1).HotFixID"' to list recent security updates, or check Windows Update history
    Affected if No security update matching this CVE (when released) is installed, and the OS build falls within the affected version ranges

A system is affected if it runs any Windows 10 or 11 version with a build number lower than the fixed builds AND has the Speech Brokered API component present, allowing a local attacker to trigger the race condition for privilege escalation.

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 the relevant Microsoft security update for this vulnerability once released. Until then, restrict local access to trusted users and monitor for unusual process behavior.

Recommended fix High confidence

Upgrade to the build number equal to or greater than the fixed version for your specific Windows release (e.g., Windows 10 22h2 build 10.0.19045.7184, Windows 11 23h2 build 10.0.22631.6936, etc.)

  1. Identify the current Windows version by running 'winver' in the Run dialog
  2. Determine which Windows 10 or 11 version is installed and match it to the affected version list
  3. Open Settings > Windows Update and check for updates
  4. Alternatively, manually download the cumulative security update for the specific Windows version from the Microsoft Update Catalog
  5. Install the appropriate update: For Windows 10 1607, install build 10.0.14393.9060 or later; For Windows 10 1809, install build 10.0.17763.8644 or later; For Windows 10 21h2, install build 10.0.19044.7184 or later; For Windows 10 22h2, install build 10.0.19045.7184 or later; For Windows 11 23h2, install build 10.0.22631.6936 or later; For Windows 11 24h2, install build 10.0.26100.8246 or later; Fo
  6. Restart the system to complete the update installation
  7. Verify the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative updates typically have minimal breaking changes; however, verify compatibility with critical business applications before deploying in production environments

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
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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