Patch tracker / CVE reference / CVE-2024-38132
CVE-2024-38132
CVE-2024-38132 is a high severity Microsoft vulnerability with a CVSS score of 7.5. Its EPSS score puts the probability of exploitation in the next 30 days at 71%. Microsoft has shipped the fix: deploy one of the 10 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Not in the CISA KEV catalog. EPSS exploit probability 71%. CVSS 7.5 (High).
This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.
CVE-2024-38132 is a second NAT denial-of-service issue, Critical 9.8 with a 71 percent EPSS score on Windows 10 1809 and Server 2019, matching its NAT siblings. The recurring NAT crash bugs this cycle argue for treating routing hosts as a focused patch group. There is no confirmed in-the-wild use or ransomware link recorded.
Do this: Include this NAT fix with the others and validate that RRAS routing hosts stay up after applying the August 2024 update.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2024-38132
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2024-38132
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5041160, KB5041571, KB5041573, KB5041578, KB5041580, KB5041585, KB5041592, KB5041773, KB5041782, KB5041828 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-38132. 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.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.