Skip to content
The November 2026 Security Update Review

The November 2026 Security Update Review

www.zerodayinitiative.com • November 11, 2026

The penultimate month of 2026 bring with it the usual storm of patches from Microsoft and Adobe. I’ve been prototyping some new ways to display this data, but as always, I’m open to suggestions. Seriously – hit me up on Bluesky if you have any ideas.If you’d rather watch the full video recap covering the entire release, you can check it out here:

Adobe Patches for November 2026

For the first part of the November release, Adobe released nine bulletins addressing 110 unique CVEs in Adobe Connect, Experience Manager, After Effects, Audition, Dimension, Photoshop, Media Encoder, Premiere, and Content Credentials SDK.

Here’s this month’s overview table:

Adobe Patches for November 2026

Obviously, if you need to prioritize, the Connect patch is the biggest and most severe bulletin this month: 24 CVEs, 18 of them Critical, with a top CVSS of 10.0. It’s Priority 2, and Adobe is not aware of any exploits in the wild. Each of the CVSS10 bugs are reachable over the network with no authentication or user interaction, and each changes scope. The other Critical-rated update for this month is in Experience Manager . It addresses 14 CVEs, which includes four Critical bugs with a CVSS 9.9 rating. Two are incorrect-authorization bugs and two are code injections. All give arbitrary code execution over the network. Each needs a low-privileged account but no user interaction, and each changes scope.

Besides the bugs already mentioned, all other patched from Adobe are a Deployment Priority 3. None of the other Adobe bugs receiving patches this month are listed as publicly known or under active attack at the time of release.

Microsoft Patches for November 2026

Well, at least it’s not a new record for Microsoft. As always, the overall count is a bit confusing, but I see 1,090 new CVEs released today. At this point, does the exact number actually matter? Regardless of the actual count, it’s huge but less than the 1,400 or so released last month. That’s two months in a row that have exceeded all years from Microsoft. As for the products affected by this release, we have Windows and Windows components; Office and Office Components; Windows networking and remote access; Windows graphics, media and printing; Windows storage file systems and drivers; .NET and Visual Studio; Windows Security and identity; Azure, cloud and identity; Exchange Server; Microsoft Dynamics; and Xbox. We’ll see how close I came to matching Microsoft’s “ Cohorts ” list.

Interestingly, there is only one bug under active attack, and none are publicly known this month. While this is encouraging, it does not mean we’re seeing less exploitation in the wild. It does mean we are seeing fewer 0-days exploited in the wild. This makes sense, as AI is better at reversing patches than it is at finding and exploiting bugs in closed-source software.

Let’s begin by covering some of the more severe and interesting patches released this month.

- CVE-2026-124194 - Microsoft Outlook Spoofing Vulnerability This is the one bug under active attack this month. It’s labeled spoofing, but the impact is bigger than the name suggests. An attacker sends a specially crafted message file and convinces a user to open it. Outlook then connects to an attacker-controlled network location without showing the usual external-content warning, which discloses the user’s NTLMv2 hash. The attacker can use that hash to authenticate as the user. The Preview Pane is not an attack vector, and the CVSS is only 6.5, so don’t let the score lull you. Microsoft marks it as exploited, so this one goes to the top of the list.

- CVE-2026-116928 - Windows Remote Code Execution Vulnerability We start with Windows , which is reached through Exchange Server. This bug allows an unauthenticated attacker to send an email with a specially crafted attachment that triggers the bug when the server automatically indexes it. The recipient never opens anything. It is a zero-click code execution bug on a high-value target. It’s also a CVSS 9.8 and clearly more severe than any of the nine patches Exchange receives this month.

- CVE-2026-119958 - Windows LDAP - Lightweight Directory Access Protocol Remote Code Execution Vulnerability This patch addresses a bug that allows an unauthenticated attacker to exploit an out-of-bounds (OOB) write (CWE-787) by sending crafted LDAP calls over the network, with no user interaction. Since it runs code in the LDAP service context, it could be quite destructive, especially on Domain Controllers. Test and deploy this one quickly.

- CVE-2026-119990 - Azure OpenAI Elevation of Privilege Vulnerability UPDATE: Microsoft has revised this bulletin to indicate there is no customer action needed. This is an odd duck. The bulletin says “Customer Action Required: Yes” for this bug, but nothing in the advisory tells customers what to do. There are no mitigations, workarounds, or customer steps. The FAQ says an unauthenticated attacker can send a crafted request over the internet to an affected Azure OpenAI service, with no account or user interaction. The impact is access to orchestration information, workflow changes, or service disruption. Hopefully, Microsoft adds some direction here soon.

- CVE-2026-119952 - Windows Schannel Remote Code Execution Vulnerability This flaw allows an unauthenticated attacker to exploit arbitrary code over a network without user interaction. Microsoft rates this bug as “Exploitation More Likely”. It is one of only a few Critical-rated patches with that rating. They also list the attack complexity as high, which is why the CVSS score is lower than the others. I would still put this near the top of my list.

- CVE-2026-95962 - Windows Virtual Filtering Platform (VFP) Remote Code Execution Vulnerability I include this one because it’s in a little-documented component. It’s not the first CVE in VFP, but it appears to be just the second. It’s a use-after-free that allows an unauthenticated attacker to get code execution on affected targets by sending a specially crafted packet to the affected service over the network. No authentication or user interaction is needed. There is a race condition here, but we see those overcome all the time at Pwn2Own. This should be an interesting component to watch.

- CVE-2026-112967 - Windows Xbox Live Networking Service Remote Code Execution Vulnerability You don’t see a lot of Xbox Live bugs, but here we are with a CVSS 9.8. This bug is a heap overflow that doesn’t need authentication or user interaction. Microsoft states the attacker can “gain remote code execution via an in-network attacker calling arbitrary endpoints.” Is this really likely? Probably not, but it’s fun to think of Xbox Live exploits in the wild.

On to those that are Wormable…

Last month saw 59 bugs that fit this definition. This month, it’s a bit less. A total of 30 of the November CVEs fit my definition of wormable. Specifically, 17 contain the advisory language describing an unauthenticated attacker executing code over the network with no authentication or user interaction required. The other 13 use variant wording or have no FAQ, but their summaries and CVSS vectors (AV:N/PR:N/UI:N) describe the same thing.

These bugs are as follows:

Message Queuing (5): CVE-2026-116710 , 119963 , 119964 , 109459 , 119967

Message Queuing (5): CVE-2026-116710 , 119963 , 119964 , 109459 , 119967

DNS (4): CVE-2026-81384 , 96092 , 96177 , 88218

DNS (4): CVE-2026-81384 , 96092 , 96177 , 88218

Two each (8): Color Management ( CVE-2026-96067 , 96078 ), DHCP Server ( CVE-2026-88243 , 72998 ), DirectMusic ( CVE-2026-95882 , 95901 ) and Xbox ( CVE-2026-112967 , 66801 )

Two each (8): Color Management ( CVE-2026-96067 , 96078 ), DHCP Server ( CVE-2026-88243 , 72998 ), DirectMusic ( CVE-2026-95882 , 95901 ) and Xbox ( CVE-2026-112967 , 66801 )

One each (13): Exchange Server ( CVE-2026-116928 ), LDAP ( CVE-2026-119958 ), Schannel ( CVE-2026-119952 ), CredSSP ( CVE-2026-119962 ), Deployment Services ( CVE-2026-119951 ), IIS ( CVE-2026-119961 ), NAT ( CVE-2026-113862 ), RPC Runtime ( CVE-2026-118737 ), Media Foundation ( CVE-2026-96157 ), iSCSI ( CVE-2026-88234 ), Virtual Filtering Platform ( CVE-2026-95962 ), eSCL Scanner ( CVE-2026-95956 ) and Modern Device Management ( CVE-2026-119945 )

One each (13): Exchange Server ( CVE-2026-116928 ), LDAP ( CVE-2026-119958 ), Schannel ( CVE-2026-119952 ), CredSSP ( CVE-2026-119962 ), Deployment Services ( CVE-2026-119951 ), IIS ( CVE-2026-119961 ), NAT ( CVE-2026-113862 ), RPC Runtime ( CVE-2026-118737 ), Media Foundation ( CVE-2026-96157 ), iSCSI ( CVE-2026-88234 ), Virtual Filtering Platform ( CVE-2026-95962 ), eSCL Scanner ( CVE-2026-95956 ) and Modern Device Management ( CVE-2026-119945 )

I may be wrong some of these, since a few advisories are light on detail. As always, I recommend testing and deploying these patches quickly, especially for network-facing services like DNS, DHCP, LDAP, and Exchange

Here’s the full list of CVEs released by Microsoft for November 2026:

* Indicates this CVE had been released by a third party and is now being included in Microsoft releases.

** Indicates this CVEs has already been resolved by Microsoft, and no further action is needed by the end user.

As with last month, I’ll do my best to summarize everything else in this release but assume there are details I miss or that will be revised after the release. I’ve tried to group these into cohorts of their own.

Local Privilege Escalations: As usual, EoP is the biggest category in the release. 425 of the EoP bugs require an attacker to already be on the box, and 245 of them hand over SYSTEM or administrator privileges. That’s what makes them the second half of nearly every attack chain. None are listed as public or under active attack, but 33 are rated “Exploitation More Likely”, which is where I’d start.

The biggest cluster is the Windows Advanced Rasterization Platform, with 36 CVEs. Twenty-eight score CVSS 8.8 with a changed scope. For these cases, an attacker running a malicious app inside an AppContainer feeds crafted graphics data to an isolated compilation service and escapes the container.

Hyper-V earns eight Critical-rated EoPs. Two of them score 8.2 with a changed scope, and the first one lets an attacker reach VTL1. Windows Remote Desktop Services (CVE-2026-119957), TPM (CVE-2026-119382), and Graphics Kernel (CVE-2026-119966) make up the rest of the local Criticals. If you run Hyper-V hosts, don’t skip these.

The rest is the usual long tail: Graphics Kernel (28), Installer (32), Kernel (18), Print Spooler (14), and DWM (9), plus smaller clusters in the Audio Service, Broadcast DVR User Service, USB drivers, and LSASS. Individually, none of these will make headlines. Collectively, they’re a very large pile of ways to become SYSTEM. Rootkits, anyone?

Office-Related Bugs: Similar to last month, Office takes a big of the release, with Word at 65 CVEs and Excel at 64. The bulk is remote code execution: 154 of the 201 are RCEs, along with 25 information disclosure bugs, 10 EoPs, and 11 spoofing bugs. Twenty-two are rated Critical. Excel has 12 of those, Word has 4, Outlook has 3, the general Office component has 2, and PowerPoint has 1. The ones to look at first are those where the Preview Pane is an attack vector, since the user never has to open the file. Ten bugs fit this description.

SharePoint Server adds 30 CVEs, and it’s a different mix from the rest of Office: 10 spoofing, 9 EoP, 7 RCE, and 3 info disclosure. The seven RCEs are mainly deserialization of untrusted data. The ones I checked need only an authenticated attacker with low-level access to send a crafted request, with no user interaction. CVE-2026-120002 is the highest score in the group at CVSS 9.9, an incorrect authorization EoP over the network. SharePoint has been a frequent target, so I wouldn’t wait for in-the-wild reports to patch.

Exchange Server: Exchange Server gets 9 bugs this month: two RCEs, four EoPs, one denial of service, and two spoofing bugs. One is Critical, and none are publicly known or exploited. The Critical RCE (8.8) needs only a low-privileged login and no user interaction, and Microsoft rates it “Exploitation More Likely”, the only Exchange bug with that rating. It’s the one I’d patch first, along with the Windows bug covered earlier. The other RCE (also 8.8) is rated “Exploitation Unlikely”. The four EoPs score between 7.2 and 8.8, and the DoS lands at 7.5. The spoofing bugs may seem least worrying, but these often turn into credential relaying, so don’t discount them. As always with Exchange, keep in mind that it’s a favorite target, so patch these on a faster schedule than the scores suggest. And good luck Exchange Admins. I know you’ve had a rough few months. ∠(‘-‘ )

SQL Server: SQL Server is the biggest single product in the release, with 59 bugs once you count the OLE DB and JDBC drivers. RCEs lead at 25, followed by 22 EoPs and 11 information disclosure bugs, with a few spoofing, bypass, DoS, and tampering bugs. All are Important, none are publicly known or exploited, and nearly all are rated “Exploitation Less Likely”.

Heap buffer overflows dominate the root causes at 24, followed by 11 SQL injection flaws. The top score is a 9.8 RCE that doesn’t require authentication, where an attacker who controls a network endpoint used by an integration package returns a crafted response. Many of the 8.8 RCEs need only a low-privileged login, and several need no user interaction. Most of the others are in the 7 to 8.8 range. If you run SQL Server, plan on testing and deploying these, since the volume suggests a lot of attention on the product.

Windows networking and remote access: Networking and remote access is a big group this month. EoP leads with 70 CVEs, followed by 48 RCEs, 30 information disclosure bugs, and 23 denial-of-service bugs. The one that surprised me is Kerberos. CVE-2026-85844 is an authentication bypass rated CVSS 9.8 that only gets an Important rating. According to the advisory, an unauthenticated attacker sends crafted Kerberos traffic and relays the resulting authentication to a domain controller, gaining SYSTEM on it with no user interaction. Don’t let the Important label fool you.

DNS has 33 CVEs between the Windows DNS and DNS Server components, 10 of them RCEs. Fifteen are information disclosure bugs, and 13 of the DNS bugs score only 4.9. The DNS Server role alone has 11. Between DHCP Server (9 bugs, 4 of them RCE) and DNS, the infrastructure services most networks run on get a lot of attention.

Some of the Critical bugs need a bit more than a network connection. The Windows TCP/IP RCE and the Function Discovery SSDP Provider RCE are both use-after-free bugs reached over an adjacent network, rated 7.5. The SMB Server bug in srvnet.sys also scores 7.5, but it needs a login and a won race condition. Race conditions get beaten at Pwn2Own all the time, so I wouldn’t count on that.

The client side is worth a look too. Remote Desktop Client has 12 CVEs, including four RCEs, where an attacker hosts a malicious server and convinces a user to connect. The NFS client follows the same pattern, with two RCEs and four additional bugs. The Remote Desktop Services and Gateway components add 7 more, including one authenticated RCE.

Azure, cloud and identity: Azure and identity bugs are a small slice of the release this month, with a mere 52 in total. Four are rated Critical: Azure OpenAI, Azure Managed Grafana, and two Active Directory Domain Services bugs.

The scariest numbers belong to Azure OpenAI (9.8, missing authentication on a critical function) and two 9.9s in Microsoft Identity Manager and Azure DevOps. The Identity Manager bug is an EoP, and the DevOps one is an RCE. Cloud-service bugs often show up with big scores and nothing to deploy. Don’t assume that here. Microsoft’s data lists every one of these as “Customer Action Required: Yes”, so I’d verify each one before dismissing it. The Active Directory Domain Services pair is the one to watch for on-prem teams. One is an RCE at 8.8 and the other is a Critical EoP, and both are rated “Exploitation More Likely”.

Windows graphics, media and printing : EoP bugs dominate this group, with 163 of the 213 bugs. Another 26 are information disclosure bugs and 24 are RCEs. Only six are rated Critical: Graphic Fonts and the Raw Image Extension (both 8.8 RCEs), a Codecs Library RCE, a Print Spooler RCE, and two Graphics Kernel EoPs.

The biggest clusters are the Advanced Rasterization Platform (37), the Graphics Kernel (35), Print Spooler (20), and Desktop Window Manager (9), with the Win32K, audio, and Broadcast DVR components behind them. The scariest scores are in the media parsers, not graphics. DirectMusic, Media Foundation, and Color Management each have RCEs scoring 9.8. The 24 RCEs are spread across the Codecs Library, DirectMusic, Color Management, Media Foundation, and the XPS converter, among others. Most are on the wormable list, so look there before you triage them. The other piece worth noting is the Raw Image Extension, where a bug can fire just by viewing a folder with a malicious RAW file in it

Windows storage file systems and drivers : EoP leads again here at 80 bugs, followed by roughly 15 RCEs and 16 information disclosure bugs. Only one is rated Critical, an EoP in the TPM. Everything else lands at Important. The scariest scores are in the storage stack. iSCSI has a 9.8 RCE and is on the wormable list. The Storage Spaces Controller adds three more 8.8 RCEs. Windows Storage itself is the biggest component, and over half of its bugs are RCEs. The rest of the group is a long tail across NTFS, USB drivers, the Overlay Filter, Storport, the Cloud Files filter, and HID. two dozen bugs need physical access, which is mostly the USB, HID, and BitLocker side of the group. Those are lower risk for most enterprises but matter for kiosks and shared machines.

.NET and Visual Studio: Developer tooling is a mid-sized group this month with a paltry 44 bugs, and none of them break out of the Important rating. RCEs and security feature bypasses lead at 12 each, with denial of service (10), EoPs (6), and information disclosure (4) behind them. Visual Studio Code is the story again, with 19 bugs. Almost all of them need user interaction, typically opening something malicious. Microsoft rates two of the VS Code bugs, one RCE and one bypass, “Exploitation More Likely”, the only ones in this group with that rating. Remember that the editor sits on developer machines full of credentials and source, so I’d treat that as a priority. The ASP.NET Core and .NET bugs are quieter. ASP.NET Core has 15 bugs, .NET has 12, split among DoS, EoP, bypass, and two RCEs. The rest are PowerShell, .NET Aspire, JScript, and a GitHub Copilot extension, in keeping with the year’s steady trickle of AI-adjacent tools.

Windows Security and identity : This is a small group, and EoP carries it with 30 of the roughly 50 bugs. The rest is a mix of denial of service (8), information disclosure (4), security feature bypass (3), and one spoofing bug. Only one is rated Critical: an RCE in Microsoft Defender (8.8). The standout is Kerberos. It’s covered in the networking section, but I’d put it near the top of the list overall because it lets an unauthenticated attacker become SYSTEM on a domain controller. The Defender RCE also needs a closer look. It requires user interaction, but it hits the product people count on to catch the attackers. The rest is the usual: credential handling, sign-in, and firewall bugs, plus a pair of Secure Kernel Mode issues.

Microsoft Dynamics: Dynamics adds just one bug this month: an information disclosure in Dynamics 365 on-premises (6.5). It is not publicly known or exploited.

What’s left is the Windows plumbing: Installer, Kernel, Shell, and a long list of single-bug services such as Task Scheduler, WMI, Performance Counters, Event Viewer, and Sandbox. EoP leads with 51 of the roughly 120, followed by 36 information disclosure bugs, 12 RCEs, and a few tampering, bypass, and spoofing bugs. None are Critical, and none are publicly known or exploited.

No new advisories are being released this month.

The final Patch Tuesday of the year will be on December 8. Regardless of how big (or how small!) the release may be, I’ll be back to do my best to discern what you need to know. Until then, stay safe, happy patching, and may all your reboots be smooth and clean!