Patch tracker / KB5046616

KB5046616: Windows Server 2022 Security Update (November 2024)

KB5046616 is a Critical security update for Windows Server 2022, released 2024-11-12. It closes 37 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV) and linked to ransomware, so this is a deploy-first update. The most likely of them to be attacked is CVE-2024-43530, which FIRST.org rates at 82% probability of exploitation in the next 30 days.

Update summary

CriticalCISA KEVRansomware
2024-11-12
Released
37
CVEs fixed
9.8
Max CVSS
Critical
Severity
Deploy immediately
This update fixes vulnerabilities confirmed exploited in the wild, including ransomware-linked CVEs.

Fixes 37 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 82%. One is linked to ransomware. Among the top 10% of tracked Microsoft updates by EPSS exploit probability.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

A newer security update for Windows Server 2022 has shipped since this one: KB5073695 (2026-01-13). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.

Senserva found thisread these before you deploy broadly

Microsoft documents 1 known issue with this update.

  • |

The full text, quoted from Microsoft

Senserva AI Opinion for KB5046616

KB5046616 is the November 12, 2024 rollup for Windows Server 2022 (including Server Core) and Windows 10 version 21H2, fixing 37 CVEs including one rated Critical at CVSS 9.8 with an 82 percent EPSS score. At least one of these CVEs is listed in the CISA Known Exploited Vulnerabilities catalog and is linked to ransomware activity, meaning attackers are actively using it in the wild. Domain controllers and Server Core hosts running Server 2022 are prime targets because the high EPSS score signals a strong likelihood of exploitation attempts.

Do this: Deploy KB5046616 to all Windows Server 2022 and Windows 10 21H2 systems now, prioritizing internet-facing and Server Core hosts given the ransomware-linked KEV entry.

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

Senserva AI Opinion and rich prompt for KB5046616

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for KB5046616

Released
2024-11-12
Last changed
2024-11-12
Changes tracked
1

Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.

Check if KB5046616 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5046616 (checked 2026-08-11). Verify against the article before acting.

|

| Symptom

| Workaround

| Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process.This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro editions of Windows are affected.

| This issue is addressed in KB5053603 .

CVEs fixed by this update

Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.

CVESeverityCVSSEPSSExploited
CVE-2024-49039High8.882%KEV Ransomware
CVE-2024-43451Medium6.582%KEV
CVE-2024-43639Critical9.882%No
CVE-2024-43620High8.882%No
CVE-2024-43621High8.882%No
CVE-2024-43622High8.882%No
CVE-2024-43624High8.882%No
CVE-2024-43627High8.882%No
CVE-2024-43628High8.882%No
CVE-2024-43635High8.882%No
CVE-2024-43447High8.182%No
CVE-2024-43625High8.182%No
CVE-2024-43516High7.882%No
CVE-2024-43528High7.882%No
CVE-2024-43530High7.882%No
CVE-2024-43623High7.882%No
CVE-2024-43626High7.882%No
CVE-2024-43629High7.882%No
CVE-2024-43630High7.882%No
CVE-2024-43636High7.882%No
CVE-2024-43640High7.882%No
CVE-2024-43641High7.882%No
CVE-2024-43644High7.882%No
CVE-2024-49019High7.882%No
CVE-2024-49046High7.882%No
CVE-2024-43450High7.582%No
CVE-2024-43452High7.582%No
CVE-2024-43642High7.582%No
CVE-2024-43511High7.082%No
CVE-2024-43449Medium6.882%No
CVE-2024-43634Medium6.882%No
CVE-2024-43637Medium6.882%No
CVE-2024-43638Medium6.882%No
CVE-2024-43643Medium6.882%No
CVE-2024-43631Medium6.782%No
CVE-2024-43646Medium6.782%No
CVE-2024-38203Medium6.282%No

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.