Patch tracker / CVE reference / CVE-2024-43581

CVE-2024-43581

CVE-2024-43581 is a critical severity Microsoft vulnerability with a CVSS score of 9.0. Its EPSS score puts the probability of exploitation in the next 30 days at 67%. Microsoft has shipped the fix: deploy one of the 7 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Critical

Risk summary

9.0

CVSS

67%

EPSS, 30 days

Critical

Severity

Senserva AI Opinion for CVE-2024-43581

Microsoft OpenSSH for Windows on Windows 10 1809 and Server 2019 exposes a remote-code-execution flaw scored 9.0 with 61 percent EPSS. OpenSSH is often deployed for remote administration and is network-reachable, so an RCE in it directly threatens management access. Hosts running the Windows OpenSSH server are the ones in scope.

Do this: Patch the OpenSSH for Windows component on 1809 and Server 2019 hosts that run the SSH server, and restrict SSH exposure to trusted networks.

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

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

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-43581 (source: https://senserva.com/cve/CVE-2024-43581.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-43581: Critical severity Microsoft vulnerability, CVSS 9.0
- EPSS 30-day exploitation probability: 67%
- Actively exploited (CISA KEV): no
- Fixed by: KB5044273, KB5044277, KB5044280, KB5044281, KB5044284, KB5044285, KB5044288
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 67%).

Fixed by KB5044273 and 6 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-43581

Published

2024-10-08

Last revised

2024-10-08

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 67%. CVSS 9.0 (Critical).

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

Official patch(es) for CVE-2024-43581

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5044273, KB5044277, KB5044280, KB5044281, KB5044284, KB5044285, KB5044288 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-43581. 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.

KB5044273 KB5044277 KB5044280 KB5044281 KB5044284 KB5044285 KB5044288

Affected products

Fixed by the same updates

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

CVE-2024-43572 CVE-2024-43573 CVE-2024-43511 CVE-2024-43516 CVE-2024-43528 CVE-2024-43582 CVE-2024-43583 CVE-2024-20659

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.