Patch tracker / CVE reference / CVE-2024-43642

CVE-2024-43642

CVE-2024-43642 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 82%. Microsoft has shipped the fix: deploy one of the 6 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Critical

Risk summary

9.8

CVSS

82%

EPSS, 30 days

Critical

Severity

Senserva AI Opinion for CVE-2024-43642

This SMB denial-of-service vulnerability is notable for reaching Windows Server 2025 and 2022, including Server Core, at Critical 9.8 with an 82 percent EPSS score. SMB is a core file-sharing service exposed on most Windows servers, so a crash bug here can be triggered by any client that can reach port 445. It is absent from CISA KEV and has no ransomware association yet.

Do this: Patch Server 2025 and 2022 file servers, and ensure SMB port 445 is never reachable from the internet or untrusted network segments.

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

Senserva AI Opinion and rich prompt for CVE-2024-43642

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-2024-43642 (source: https://senserva.com/cve/CVE-2024-43642.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-43642: Critical severity Microsoft vulnerability, CVSS 9.8
- EPSS 30-day exploitation probability: 82%
- Actively exploited (CISA KEV): no
- Fixed by: KB5046616, KB5046617, KB5046618, KB5046633, KB5046696, KB5046698
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.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 82%).

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

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Full tracking and change history for CVE-2024-43642

Published

2024-11-12

Last revised

2024-11-12

Changes tracked

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 82%. CVSS 9.8 (Critical).

This CVE is among the top 10% of tracked Microsoft CVEs by EPSS exploit probability.

Official patch(es) for CVE-2024-43642

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5046616, KB5046617, KB5046618, KB5046633, KB5046696, KB5046698 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-43642. 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.

KB5046616 KB5046617 KB5046618 KB5046633 KB5046696 KB5046698

Affected products

Fixed by the same updates

If you are patching CVE-2024-43642, the same updates also fix these:

CVE-2024-43451 CVE-2024-49039 CVE-2024-38203 CVE-2024-38264 CVE-2024-43447 CVE-2024-43449 CVE-2024-43450 CVE-2024-43452

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.