Patch tracker / CVE reference / CVE-2026-32090

CVE-2026-32090

CVE-2026-32090 is a Microsoft vulnerability that Microsoft rates Important, with a CVSS score of 7.8 (High). Microsoft has shipped the fix: deploy one of the 9 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Risk summary

High

7.8

CVSS v3

3.5%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 3.5%. CVSS 7.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-32090

The second Speech Brokered API escalation stretches further across builds, covering Windows 11 Version 26H1 down to Windows 10 Version 1809 at Critical (CVSS 9.8) severity with EPSS at 64 percent. A bug spanning from the newest release back to 1809 has likely existed in the codebase for years, and its broker context makes it useful for escaping app containers. Both speech flaws are fixed together in the monthly updates.

Do this: Patch across the full client range, making sure the new 26H1 ring and the legacy 1809 ring both show compliant.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-32090

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-32090 (source: https://senserva.com/cve/CVE-2026-32090.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2026-32090: Microsoft vulnerability, Microsoft rating Important, CVSS 7.8 (High)
- EPSS 30-day exploitation probability: 3.5%
- Actively exploited (CISA KEV): no
- Fixed by: KB5082052, KB5082060, KB5082063, KB5082123, KB5082142, KB5082198, KB5082200, KB5083768, KB5083769
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed as of 2026-10-19: not in the CISA KEV catalog, EPSS 4%.

Fixed by KB5082052 and 8 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-32090

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5082052, KB5082060, KB5082063, KB5082123, KB5082142, KB5082198, KB5082200, KB5083768, KB5083769 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2026-32090. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5082052 KB5082060 KB5082063 KB5082123 KB5082142 KB5082198 KB5082200 KB5083768 KB5083769

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-33824 CVE-2026-26167 CVE-2026-26178 CVE-2026-32157 CVE-2026-32225 CVE-2026-27928 CVE-2026-32091 CVE-2026-32162

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.