Patch tracker / CVE reference / CVE-2026-33099
CVE-2026-33099
Updated July 21, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Critical severity Microsoft vulnerability, CVSS 9.8. Fixed by 9 Microsoft security updates.
All about CVE-2026-33099: the Senserva AI read, whether it is exploited, the official patches, its change history, and the questions admins ask.
CVE-2026-33099 is a critical severity Microsoft vulnerability with a CVSS score of 9.8. Its EPSS score puts the probability of exploitation in the next 30 days at 64%. 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.
Risk summary
Senserva provides Three Free Unlimited Audits, including all tenants and full Claude MCP.Start my Audit
Senserva AI Opinion for CVE-2026-33099
Another WinSock Ancillary Function Driver elevation of privilege bug, this one affecting Windows 10 version 1809 and Windows Server 2019 rather than the 26H1 line, rounds out the set of Critical, 64 percent EPSS driver flaws in this disclosure. Given how many separate CVEs hit this one driver in this release, older Server 2019 fleets running unpatched builds carry meaningfully more exposure than a single-bug count would suggest. Not confirmed exploited or ransomware-linked.
Do this: Include Server 2019 and Windows 10 1809 hosts in the WinSock driver patch rollout, confirming all the distinct AFD CVEs in this cycle are addressed together.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-33099
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-33099
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
Exploitation and severity
Not in the CISA KEV catalog. EPSS exploit probability 64%. CVSS 9.8 (Critical).
This CVE is among the top half of tracked Microsoft CVEs by EPSS exploit probability.
Official patch(es) for CVE-2026-33099
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5082052, KB5082060, KB5082123, KB5082126, KB5082127, KB5082142, KB5082198, KB5082200, 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-33099. 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.
Affected products
Common questions about CVE-2026-33099
Is CVE-2026-33099 actively exploited?
It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score puts the probability of exploitation in the next 30 days at 64%.
What patch fixes CVE-2026-33099?
Microsoft fixed CVE-2026-33099 in KB5082052, KB5082060, KB5082123, KB5082126, KB5082127, KB5082142, KB5082198, KB5082200, KB5083769. Download from the Microsoft Update Catalog, or let Intune, Windows Update, or WSUS deliver it.
Which products are affected by CVE-2026-33099?
Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows 11 Version 26H1 for ARM64-based Systems, Windows 11 version 26H1 for x64-based Systems, Windows Server 2019.
Can I ask my own AI about CVE-2026-33099?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-33099's key facts: severity, CVSS, EPSS exploit probability, CISA KEV status, and the fixing KB. Copy it into Claude, ChatGPT, or Copilot for a triage plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Fixed by the same updates
If you are patching CVE-2026-33099, the same updates also fix these:
Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.
