Security News ZDI: The November 2026 Security Update Review

Gandalf_The_Grey

Level 86
Verified
Honorary Member
Top Poster
Content Creator
Well-known
Forum Veteran
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 out the Patch Report webcast on our YouTube channel. It should be posted within a couple of hours after the release.
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.

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 about 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 previous 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.
Looking Ahead

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!
 
Microsoft November 2026 Patch Tuesday fixes 1,235 flaws, Outlook zero-day
Today is Microsoft's November 2026 Patch Tuesday, with security updates addressing a record-breaking 1,235 flaws, including one actively exploited Microsoft Outlook zero-day vulnerability.

This Patch Tuesday addresses 66 "Critical" vulnerabilities, 48 of which are Remote Code Execution (RCE), 15 are Elevation of Privilege (EoP), and three are Use-After-Free in Microsoft Edge.

The approximate number of bugs in each vulnerability category is listed below:
  • 536 Elevation of Privilege Vulnerabilities
  • 27 Security Feature Bypass Vulnerabilities
  • 296 Remote Code Execution Vulnerabilities
  • 157 Information Disclosure Vulnerabilities
  • 46 Denial of Service Vulnerabilities
  • 22 Spoofing Vulnerabilities
  • 142 Microsoft Edge (Chromium-based) Vulnerabilities
Of the 1,235 vulnerabilities, approximately 639 are categorized under Windows or Microsoft Windows products/components.

When BleepingComputer reports on Patch Tuesday security updates, we only count vulnerabilities released by Microsoft on Patch Tuesday itself.

Therefore, today's total excludes 108 flaws fixed earlier this month, including one Entra Device Registration, 82 Mariner, and 25 Microsoft Edge flaws.
 
Thanks, Gandalf. The practical headline is not whether the total is exactly 1,090, 1,093 or another tally—it is which vulnerable components are deployed, exposed and already being exploited. CVE counting has become a sport with surprisingly flexible rules.

My priority order would be:

  1. The actively exploited Outlook vulnerability, CVE-2026-124194. It is rated only Moderate, but reportedly allows a malicious Outlook message file to trigger a connection to an attacker-controlled location and expose NTLMv2 authentication material. The user must open the file; the Preview Pane is not an attack vector. Update affected Office installations promptly. As a backstop, organisations should confirm that outbound SMB traffic to the Internet is blocked, although that does not replace patching.
  2. Internet-facing Adobe Connect servers. Adobe’s APSB26-191 bulletin confirms a Priority 2 update covering critical, high and medium vulnerabilities with possible code execution, privilege escalation and file access. Adobe reports no known exploitation, but pre-authentication, network-reachable CVSS 10 flaws are not ones I would leave sitting around merely because nobody has been caught using them yet.
  3. Adobe Experience Manager deployments. APSB26-189 covers code execution, privilege escalation and security-feature bypass. The low-privileged-account requirement reduces exposure compared with the Connect issues, but exposed AEM systems still deserve prompt attention.
  4. Everything else according to role and exposure: identity infrastructure, Exchange, remote access, externally reachable services, then endpoints processing untrusted documents and media.

Microsoft’s proposed risk cohorts make sense for a release this large: answer common deployment and exposure questions once, then apply that context to the related CVEs. However, Microsoft explicitly describes the cohorts as provisional and exploratory, not official vulnerability categories or a replacement for reviewing active exploitation, severity, privileges and user interaction for each CVE.

The observation about AI being better at patch-diffing than discovering closed-source vulnerabilities is plausible, but it remains an explanation rather than something demonstrated by this month’s figures. One exploited zero-day at release tells us about known exploitation of unpatched flaws; it does not measure all exploitation of older or newly patched vulnerabilities.

For ordinary home users, most of the intimidating Adobe server issues are irrelevant unless they actually run those products. Install Windows and Office updates, update any installed Adobe desktop applications through their official updater, reboot, and verify that the updates completed successfully.

Sources
 

Join the discussion

Write your reply below. You'll create a free account or log in before it's posted.

Recently browsing

Members who viewed this thread in the last 5 minutes

Back
Top