Patch tracker / CVE reference / CVE-2024-30073
CVE-2024-30073
CVE-2024-30073 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 71%. Microsoft has shipped the fix: deploy one of the 17 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Critical severity Microsoft vulnerability, CVSS 9.8. Fixed by 17 Microsoft security updates.
Risk summary
Updated July 24, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2024-30073
A security feature bypass rather than direct code execution: Windows Security Zone Mapping, the mechanism that decides whether content is treated as internet or intranet, fails on systems from Windows 10 Version 1809 through Windows 11 24H2. It is rated Critical (CVSS 9.8) with 71 percent EPSS. Zone mapping bypasses defeat mark-of-the-web style protections, unlocking smoother phishing and payload delivery chains.
Do this: Deploy the update fleet-wide and audit any security exceptions that depend on zone classification, such as macro and SmartScreen policies.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2024-30073
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2024-30073
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 71%. CVSS 9.8 (Critical).
This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.
Official patch(es) for CVE-2024-30073
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5042880, KB5042881, KB5043049, KB5043050, KB5043051, KB5043055, KB5043064, KB5043067, KB5043076, KB5043080, KB5043083, KB5043087, KB5043092, KB5043125, KB5043129, KB5043135, KB5043138 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-2024-30073. 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-2024-30073
Is CVE-2024-30073 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 71%.
What patch fixes CVE-2024-30073?
Microsoft fixed CVE-2024-30073 in KB5042880, KB5042881, KB5043049, KB5043050, KB5043051, KB5043055, KB5043064, KB5043067, KB5043076, KB5043080, KB5043083, KB5043087, KB5043092, KB5043125, KB5043129, KB5043135, KB5043138. Download from the Microsoft Update Catalog, or let Intune, Windows Update, or WSUS deliver it.
Which products are affected by CVE-2024-30073?
Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows 11 Version 24H2 for ARM64-based Systems, Windows 11 Version 24H2 for x64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022.
Can I ask my own AI about CVE-2024-30073?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2024-30073'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-2024-30073, 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.