Microsoft's November 2024 Patch Tuesday fixes 96 vulnerabilities across Windows, SQL Server and Microsoft Office - 7 rated Critical, 3 publicly disclosed before the patch shipped, 3 already exploited in the wild. Patch CVE-2024-43451 first.
Why this number differs from other roundups. Microsoft's November 2024 release document lists 741 entries. 632 are Azure Linux (Mariner) OS package updates and 13 are republished Chromium fixes for Edge - neither is a Microsoft product vulnerability. The 96 above is the real Patch Tuesday set. See the breakdown →
Ranked by exploitation reality, not score alone. This month's exploited flaw is rated Important - a severity-sorted list would bury it.
Patch today
Confirmed attacks are already happening. Emergency change window.
CVE-2024-43451NTLM Hash Disclosure Spoofing VulnerabilityCVE-2024-49035Partner.Microsoft.Com Elevation of Privilege VulnerabilityCVE-2024-49039Windows Task Scheduler Elevation of Privilege VulnerabilityPatch this week
Details are already public. Working exploits typically follow within days.
CVE-2024-49019Active Directory Certificate Services Elevation of Privilege VulnerabilityCVE-2024-49040Microsoft Exchange Server Spoofing VulnerabilityPatch this cycle
No known exploitation yet, but network-reachable and high impact.
CVE-2024-43498.NET and Visual Studio Remote Code Execution VulnerabilityCVE-2024-43639Windows KDC Proxy Remote Code Execution VulnerabilitySee all 7 Critical →Most roundups quote a single number. These are three unrelated release streams.
Microsoft channel only · 96 CVEs
| Critical | 7 |
|---|---|
| Important | 87 |
| Moderate | 1 |
| Low | 0 |
| Unrated | 1 |
What an attacker gains if it works
| Remote Code Execution | 52 |
|---|---|
| Elevation of Privilege | 32 |
| Spoofing | 4 |
| Denial of Service | 4 |
| Security Feature Bypass | 2 |
| Information Disclosure | 1 |
| Other | 1 |
Where this month’s fixes concentrate - filter by any of them in the table below
Sorted by risk by default: exploited first, then publicly disclosed, then severity, then CVSS. Search by CVE, title, component or KB number.
| Title | Status | KB | |||||
|---|---|---|---|---|---|---|---|
| Important | CVE-2024-43451 | NTLM Hash Disclosure Spoofing Vulnerability | Spoofing | 6.5 | ExploitedDisclosed | Windows NTLM | 5046612 +15 |
| Critical | CVE-2024-49035 | Partner.Microsoft.Com Elevation of Privilege Vulnerability | EoP | 8.7 | Exploited | Microsoft Partner Center | — |
| Important | CVE-2024-49039 | Windows Task Scheduler Elevation of Privilege Vulnerability | EoP | 8.8 | Exploited | Windows Task Scheduler | 5046612 +9 |
| Important | CVE-2024-49019 | Active Directory Certificate Services Elevation of Privilege Vulnerability | EoP | 7.8 | DisclosedMore likely | Role: Windows Active Directory Certificate Services | 5046612 +12 |
| Important | CVE-2024-49040 | Microsoft Exchange Server Spoofing Vulnerability | Spoofing | 7.5 | DisclosedMore likely | Microsoft Exchange Server | 5049233 |
| Important | CVE-2024-49060 | Azure Stack HCI Elevation of Privilege Vulnerability | EoP | 8.8 | More likely | Azure Stack | — |
| Important | CVE-2024-43623 | Windows NT OS Kernel Elevation of Privilege Vulnerability | EoP | 7.8 | More likely | Windows NT OS Kernel | 5046612 +15 |
| Important | CVE-2024-43629 | Windows DWM Core Library Elevation of Privilege Vulnerability | EoP | 7.8 | More likely | Windows DWM Core Library | 5046613 +7 |
| Important | CVE-2024-43630 | Windows Kernel Elevation of Privilege Vulnerability | EoP | 7.8 | More likely | Windows Kernel | 5046613 +5 |
| Important | CVE-2024-43636 | Win32k Elevation of Privilege Vulnerability | EoP | 7.8 | More likely | Windows DWM Core Library | 5046612 +10 |
| Important | CVE-2024-43642 | Windows SMB Denial of Service Vulnerability | DoS | 7.5 | More likely | Windows SMB | 5046616 +5 |
| Important | CVE-2024-49033 | Microsoft Word Security Feature Bypass Vulnerability | Bypass | 7.5 | More likely | Microsoft Office Word | 5002619 |
| Critical | CVE-2024-43498 | .NET and Visual Studio Remote Code Execution Vulnerability | RCE | 9.8 | — | .NET and Visual Studio | — |
| Critical | CVE-2024-43639 | Windows KDC Proxy Remote Code Execution Vulnerability | RCE | 9.8 | — | Windows Kerberos | 5046612 +8 |
| Critical | CVE-2024-49038 | Microsoft Copilot Studio Elevation Of Privilege Vulnerability | EoP | 9.3 | — | Copilot Studio | — |
| Critical | CVE-2024-49052 | Microsoft Azure PolicyWatch Elevation of Privilege Vulnerability | EoP | 8.2 | — | Microsoft Azure Functions | — |
| Critical | CVE-2024-43625 | Microsoft Windows VMSwitch Elevation of Privilege Vulnerability | EoP | 8.1 | — | Windows VMSwitch | 5046616 +5 |
| Important | CVE-2024-43602 | Azure CycleCloud Remote Code Execution Vulnerability | RCE | 9.9 | — | Azure CycleCloud | — |
| Important | CVE-2024-5535 | OpenSSL: CVE-2024-5535 SSL_select_next_proto buffer overread | RCE | 9.1 | — | Microsoft Defender for Endpoint | — |
| Important | CVE-2024-38255 | SQL Server Native Client Remote Code Execution Vulnerability | RCE | 8.8 | — | SQL Server | 5046855 +5 |
| Important | CVE-2024-43459 | SQL Server Native Client Remote Code Execution Vulnerability | RCE | 8.8 | — | SQL Server | 5046855 +5 |
| Important | CVE-2024-43462 | SQL Server Native Client Remote Code Execution Vulnerability | RCE | 8.8 | — | SQL Server | 5046855 +5 |
| Important | CVE-2024-43620 | Windows Telephony Service Remote Code Execution Vulnerability | RCE | 8.8 | — | Windows Telephony Service | 5046612 +15 |
| Important | CVE-2024-43621 | Windows Telephony Service Remote Code Execution Vulnerability | RCE | 8.8 | — | Windows Telephony Service | 5046612 +15 |
| Important | CVE-2024-43622 | Windows Telephony Service Remote Code Execution Vulnerability | RCE | 8.8 | — | Windows Telephony Service | 5046612 +15 |
The same five steps every month, in the order that reduces risk fastest.
CVE-2024-43451 is rated Important and scores 6.5 - a CVSS-sorted list would bury the one flaw attackers are already using. Sort by exploited, then publicly disclosed, then severity.
Patch Management vs Vulnerability Management: What's the Difference? →This release means 35 distinct update packages to deploy. Pilot on ring 0 within 24 hours and widen to production by day seven - never push the whole set everywhere at once.
What is Ring-Based Patch Deployment? A Guide to Progressive Rollouts →The Patch Management Lifecycle: 6 Stages from Discovery to Verification →Check the Windows release health dashboard before promoting past ring 1, and have the rollback path written down before you need it. Kernel, networking and authentication fixes are the ones that historically break things.
12 Patch Management Best Practices for 2026 →13 Chromium fixes for Edge shipped alongside this release on their own updater, and Adobe, SAP and Oracle release in the same week. OS-only patching leaves most of your real attack surface untouched.
What is Third-Party Patch Management and Why OS Patching Isn't Enough →Confirm the patch is actually present on each endpoint rather than trusting that "deployment succeeded". Keep the resulting report - it is the artefact auditors ask for, and reconstructing it later is far more work than capturing it now.
Patch Management: The Complete Guide →Trinetri does steps two through five automatically - detecting the 35 KB articles across every endpoint, staging them in rings, verifying installed state and producing the compliance evidence. See patch management →
Every month back to October 2024, with the same breakdown and the full CVE list.
Patch Tuesday falls on the second Tuesday of every month, with updates going live at 10:00 a.m. Pacific Time. Microsoft introduced the practice in October 2003, following the Blaster worm, to cut distribution costs and give administrators a predictable cadence instead of patches arriving at random. The 10:00 a.m. timing is deliberate: it leaves a full working week to remediate before the weekend. Internally Microsoft calls it the "B" release; optional "C" and "D" preview releases follow later in the month. The next Patch Tuesday is September 8, 2026.
Microsoft fixed 96 vulnerabilities in November 2024, across Windows, SQL Server, Microsoft Office and Azure. 7 are rated Critical, 3 were publicly disclosed before the patch shipped, and 3 were already being exploited. Note that Microsoft's release document lists 741 entries in total, but 632 of those are Azure Linux package updates and 13 are republished Chromium fixes for Edge, which is why other sources sometimes quote a much larger number.
Exploit Wednesday is the day after Patch Tuesday. Attackers compare the newly released patches against the previous version to locate the flaw each one fixes, then build working exploits from that difference - often within 24 to 48 hours. It is the reason the deployment window matters as much as the patch itself: every hour a Critical remote code execution fix sits undeployed is an hour of measurable exposure.
A workable target for most organisations: actively exploited vulnerabilities within 24 hours, publicly disclosed ones within 72 hours, remaining Critical fixes within seven days, and everything else within the month. CISA's Known Exploited Vulnerabilities catalogue sets binding deadlines for US federal agencies and is a reasonable benchmark for everyone else. Stage the rollout in rings rather than deploying everywhere at once, so a regression is caught on a pilot group instead of in production.
An out-of-band update is a patch released outside the monthly cycle because the risk will not wait for the next Patch Tuesday. Microsoft issues them for actively exploited flaws with no mitigation - most famously during the WannaCry outbreak in 2017, when it took the unusual step of patching versions of Windows that were already out of support.
Yes. Adobe aligned its releases with Patch Tuesday in November 2012, and both SAP's Security Patch Day and Oracle's quarterly Critical Patch Updates are coordinated to the same week. Part of the reason is defensive: staggered releases let attackers reverse-engineer one vendor's patch to find the same underlying flaw in another's still-unpatched product. For IT teams it means the second Tuesday is rarely just a Microsoft problem.
Edge is built on Chromium, so most of its security fixes originate with the Chromium project and are republished by Microsoft under their own CVE identifiers. They ship on Chromium's cadence rather than the Patch Tuesday cycle, and they are delivered by Edge's own updater rather than Windows Update. Counting the 13 Edge entries alongside Microsoft product fixes would inflate the headline number and imply work for your Windows Update rings that does not exist.
Experience how Trinetri transforms endpoint chaos into clarity. Try the 30 minute demo session, our experts will walk you through how AI-powered automation, real-time visibility, and unified control can secure your entire hybrid environment, without the overhead.
