November Patch Tuesday Fixes Outlook Zero-Day

Microsoft patched CVE-2026-124194, an actively exploited Outlook spoofing bug that can leak NTLMv2 hashes, in a November release outlets size between roughly 1,090 and 1,235 flaws.

Microsoft's November 2026 Patch Tuesday, released November 10, patched 63 critical vulnerabilities and one flaw already being exploited in the wild: CVE-2026-124194, an Outlook spoofing bug that can leak a victim's NTLMv2 password hash to an attacker. The total patch count itself is contested — outlets covering the release report anywhere from roughly 1,090 to 1,235 vulnerabilities fixed, depending on how each counts cloud-service and third-party advisories bundled into the release. What is not contested is that the Outlook bug needs to be patched now, and that federal agencies have a CISA deadline of November 24, 2026 to do it.

Quick facts: November 2026 Patch Tuesday

  • Release date: November 10, 2026 ("2026-Nov" in Microsoft's Security Update Guide)
  • Actively exploited: CVE-2026-124194 (Microsoft Outlook Spoofing Vulnerability) — the only entry Microsoft marks "Exploitation Detected" this cycle
  • Total vulnerabilities: reported between roughly 1,090 and 1,235, depending on the outlet and methodology — see "How big is this Patch Tuesday, really?" below
  • Critical-rated bugs: 63, cited consistently across secondary coverage
  • CISA KEV deadline: November 24, 2026 for federal civilian agencies to remediate CVE-2026-124194

The Outlook zero-day: CVE-2026-124194

CVE-2026-124194 is officially titled the "Microsoft Outlook Spoofing Vulnerability." According to Microsoft's own Security Update Guide entry, the root cause is that "Product UI does not warn user of unsafe actions in Microsoft Office Outlook" — meaning a specially crafted message file can get Outlook to connect to an attacker-controlled network location without showing the external-content warning that would normally tip off the user. That silent connection attempt is what allows the attacker to capture the victim's NTLMv2 hash for later cracking or relay.

Microsoft's scoring for the bug is CVSS 3.1 base 6.5 (Moderate), with a temporal score of 6.2 reflecting that exploit code is mature and a fix is available. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:H/RL:O/RC:C — network attack vector, low complexity, no privileges required, but user interaction is required and it was not publicly disclosed before patching. Despite the Moderate label, Microsoft's own advisory lists the exploitation status as "Exploitation Detected," meaning it has already been used in real attacks, not merely demonstrated as a proof of concept.

Several researchers quoted in trade coverage have pushed back on the idea that a 6.5 score means this is a low priority. Dustin Childs of Trend's Zero Day Initiative put it bluntly in comments reported by The Register: "It's labeled spoofing, but the impact is bigger than the name suggests." Nick Carroll of Nightwing, cited by CSO Online, was more direct: "Don't let the low score fool you."

How the attack works

The exploitation chain is straightforward by zero-day standards, which is likely part of why it has already been weaponized:

  1. An attacker sends a specially crafted message file to the target, typically via email.
  2. The victim opens the file in a vulnerable version of Outlook. Opening and interacting with the file is required — this is not a zero-click bug.
  3. Outlook's UI fails to display the external-content warning that would normally appear before connecting to a remote resource.
  4. Outlook silently reaches out to an attacker-controlled network location, which can capture the victim's NTLMv2 authentication hash during that connection attempt.
  5. The attacker can then attempt to crack the hash offline or relay it to authenticate as the victim against other services.

Microsoft's advisory notes that exploitation requires network connectivity and user interaction, and that no authentication is required of the attacker. According to eSecurityPlanet's reporting on Microsoft's guidance, the Outlook Preview Pane is not an attack vector for this particular flaw — the victim has to actually open the crafted file, not merely preview it. That is a meaningfully narrower attack surface than a preview-pane bug, but it is still well within reach of a competent phishing campaign, which is presumably how it is already being exploited.

This kind of credential-hash theft is conceptually similar to other authentication-relay and credential-harvesting techniques; if your organization is reviewing its exposure to hash-theft or credential-pressure attacks generally, it's worth also revisiting how MFA fatigue attacks exploit the human side of authentication, since both ultimately aim to get a working credential into an attacker's hands rather than breaking cryptography outright.

Who's affected and what to update

The affected product, per Microsoft's own listing, is Microsoft Office Outlook. Secondary reporting narrows this further: CSO Online lists Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024 as the affected builds. Notably, the fix ships as an Office security update rather than through the Windows cumulative update channel — organizations that only deploy the monthly Windows cumulative update and skip Office-specific updates will remain exposed even after a "fully patched" Windows rollout. IT teams should confirm their patch management tooling is actually pulling and deploying the Office-channel update, not just the OS-level one.

Because the flaw was not publicly disclosed before Microsoft shipped a fix, and because it is already listed as actively exploited, there is no meaningful grace period here. CISA has added CVE-2026-124194 to its Known Exploited Vulnerabilities (KEV) catalog, per Qualys's Patch Tuesday writeup, with federal civilian agencies required to remediate by November 24, 2026 under Binding Operational Directive 22-01. Enterprises outside the federal mandate should treat that same date as a practical deadline, not just a compliance one.

How big is this Patch Tuesday, really?

Pinning down the exact scale of November's release is harder than it should be, and it's worth being upfront about that rather than picking one number and presenting it as settled fact. Coverage of this release gives noticeably different totals:

Outlet / sourceReported total vulnerabilitiesCritical count cited
Dark Reading~1,09363
The Register / SecurityWeek1,09463
CSO Online1,09463
Rapid7 (via itwire)~1,09263
Qualys headline figure1,235 (across Microsoft's release)63
Qualys internal summary table1,09463
TechRepublic1,23563

Even within a single outlet's own coverage, the numbers can disagree — Qualys's November write-up cites a headline figure of 1,235 vulnerabilities addressed across Microsoft's release elsewhere in the same post, while its own Microsoft Release Summary table tallies to roughly 1,094. The likely explanation is methodology: some counts include every CVE touching any Microsoft product that month (including Chromium-based Edge, which alone reportedly accounts for over 140 of the entries, and Microsoft's cloud services patched separately from the traditional update channel), while others count only vulnerabilities shipped through the traditional Patch Tuesday update channel for Windows and Office. Readers should treat "roughly 1,090 to 1,235" as the honest range rather than any single number as gospel. The one figure that holds steady across every outlet we found is 63 critical-rated vulnerabilities.

Other critical vulnerabilities to prioritize

CVE-2026-124194 is the headline because it's being actively exploited, but it is rated only Moderate. Several other bugs patched this cycle carry the maximum CVSS 9.8 score and deserve attention from any team doing risk-based patching, even though none of them are currently known to be exploited:

CVEComponentCVSSExploitation statusWhy it matters
CVE-2026-124194Microsoft Outlook6.5Exploited in the wildOnly actively exploited bug this cycle; leaks NTLMv2 hashes
CVE-2026-119958Windows LDAP9.8Not observedUnauthenticated RCE that could compromise domain controllers
CVE-2026-116928Windows Search / Exchange attachment indexing9.8Not observedExchange auto-processes attachments for indexing, raising zero-click concern
CVE-2026-118207Exchange Server9.8Not observedReportedly triggerable by email
CVE-2026-112967Xbox Live Networking Service9.8Not observedHeap overflow RCE, no authentication or user interaction needed on the same network
CVE-2026-119990Azure OpenAI9.8Not observedElevation of privilege; patched automatically by Microsoft on the cloud side

The LDAP flaw (CVE-2026-119958) in particular echoes a pattern security teams have seen before with domain-controller-facing services: an unauthenticated, network-reachable memory-corruption bug in core directory infrastructure is about as bad as it gets. It's a similar risk profile to other recent out-of-bounds and remote-code-execution flaws that pushed organizations into emergency patch cycles, such as the critical RCE Apache patched in mod_http2 earlier this cycle.

CISA's Known Exploited Vulnerabilities deadline

CVE-2026-124194's addition to CISA's KEV catalog puts it in the same operational category as other recent KEV entries that security teams have had to race against a clock for. Federal civilian agencies must remediate by November 24, 2026, and plenty of private-sector security teams use the same KEV catalog as their own internal patch-priority signal, deadline included. That makes this the second KEV entry this month with a November 24 deadline that security teams are tracking alongside each other — Pandromeda covered a similar fast-turnaround mandate with CISA's Cisco BroadWorks XXE KEV addition, which carries the identical November 24 cutoff. Teams juggling both should check whether either product is in their environment before the deadline, not after.

What security researchers are saying

Beyond the specifics of CVE-2026-124194, several researchers used this month's release to comment on the sheer scale of modern Patch Tuesdays. Dustin Childs told outlets covering the release that automated bug-hunting tooling has "permanently reset patch volume" — a reference to the fact that Microsoft and other vendors have increasingly leaned on automated fuzzing and AI-assisted bug discovery internally, producing months with four-digit vulnerability counts that would have been unheard of a few years ago. Tyler Reguly of Fortra offered a useful corrective to critical-count anxiety, noted by CSO Online: "A vulnerability isn't critical if you don't have the impacted software deployed" — a reminder that raw CVE counts matter less than which of those CVEs actually touch your environment.

That framing is a good match for the Outlook bug specifically. It affects a huge installed base (Outlook is close to ubiquitous in enterprise environments), it's already being exploited, and it's cheap to patch — which is why multiple outlets independently flagged it as the thing to act on this month even though its CVSS score alone wouldn't normally put it at the top of a risk-sorted list.

What to patch first

Given everything above, a reasonable prioritization for November's release looks like this:

  1. CVE-2026-124194 (Outlook) first, today. It's already being exploited, it's on CISA's KEV list with a November 24 deadline, and the fix is a single Office security update — not a disruptive OS-level change. Confirm your Office update channel is actually deploying it, since the Windows cumulative update alone will not.
  2. Domain-controller- and Exchange-facing critical RCEs next. CVE-2026-119958 (LDAP) and CVE-2026-118207 (Exchange) are unauthenticated, network-reachable, and rated 9.8 — treat them with the same urgency as any other pre-authentication RCE against core infrastructure, even without evidence of in-the-wild exploitation yet.
  3. Anything exposing Windows Search/indexing to untrusted attachments (CVE-2026-116928). Attachment-processing bugs have a track record of becoming practical zero-click vectors once researchers (or attackers) build working proof-of-concept exploits.
  4. Everything else, triaged by actual exposure. Not every environment runs Xbox Live Networking Service or depends on Azure OpenAI directly; don't burn a maintenance window on components you don't run. Reguly's point above applies broadly: match the patch queue to your actual software inventory, not to the raw CVE count.
  5. Reassess your detection and response posture for credential theft generally. An NTLM-hash-leaking bug like CVE-2026-124194 is a reminder that authentication material, not just endpoints, needs monitoring. If your organization doesn't already have a response plan for a credential-exposure incident, it's worth reviewing the steps to take after a data breach before you need them under pressure.

Expect the usual follow-on activity: Microsoft's advisory for CVE-2026-124194 may be revised as more telemetry comes in, and it would not be surprising if additional proof-of-concept detail or a second wave of exploitation attempts surfaces in the weeks after this release, as has happened with past actively-exploited Patch Tuesday entries. Pandromeda will update this piece if Microsoft revises the advisory or if the total vulnerability count is clarified by a consolidated, after-the-fact tally.

FAQ

Is CVE-2026-124194 being actively exploited?
Yes. Microsoft's own Security Update Guide lists its exploitation status as "Exploitation Detected," meaning it has observed real-world attacks using this flaw, not just proof-of-concept research. It was not publicly disclosed before the patch shipped.

What does CVE-2026-124194 actually let an attacker do?
A crafted message file can trick Outlook into connecting to an attacker-controlled network location without showing its usual external-content warning. That connection can expose the victim's NTLMv2 password hash, which an attacker can try to crack offline or relay to impersonate the victim against other services.

How many vulnerabilities did Microsoft actually patch in November 2026?
It depends who you ask. Figures in secondary coverage range from roughly 1,090 to 1,235, with most outlets landing between 1,092 and 1,094 and Qualys and TechRepublic citing a higher 1,235 figure. The discrepancy likely comes down to what each outlet counts — Chromium-based Edge CVEs and cloud-service advisories are counted differently by different trackers. The critical count of 63 is consistent across sources.

Do I need to install a separate update, or does the Windows cumulative update cover CVE-2026-124194?
Reporting indicates the fix ships through an Office security update rather than the Windows cumulative update. Confirm your patch management process is deploying Office updates specifically, not just the monthly Windows OS rollup.

Is the Outlook Preview Pane affected?
According to reporting on Microsoft's guidance, the Preview Pane is not an attack vector for this bug — a user has to actually open the crafted message file, not simply preview it in the reading pane.

What's the CISA KEV deadline for this vulnerability?
CISA added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog with a remediation deadline of November 24, 2026 for federal civilian agencies. Private-sector organizations commonly treat KEV deadlines as a practical benchmark even when not legally bound by them.

Frequently asked questions

Is CVE-2026-124194 being actively exploited?

Yes. Microsoft's own Security Update Guide lists its exploitation status as "Exploitation Detected," meaning it has observed real-world attacks using this flaw, not just proof-of-concept research. It was not publicly disclosed before the patch shipped.

What does CVE-2026-124194 actually let an attacker do?

A crafted message file can trick Outlook into connecting to an attacker-controlled network location without showing its usual external-content warning. That connection can expose the victim's NTLMv2 password hash, which an attacker can try to crack offline or relay to impersonate the victim against other services.

How many vulnerabilities did Microsoft actually patch in November 2026?

It depends who you ask. Figures in secondary coverage range from roughly 1,090 to 1,235, with most outlets landing between 1,092 and 1,094 and Qualys and TechRepublic citing a higher 1,235 figure. The discrepancy likely comes down to what each outlet counts — Chromium-based Edge CVEs and cloud-service advisories are counted differently by different trackers. The critical count of 63 is consistent across sources.

Do I need to install a separate update, or does the Windows cumulative update cover CVE-2026-124194?

Reporting indicates the fix ships through an Office security update rather than the Windows cumulative update. Confirm your patch management process is deploying Office updates specifically, not just the monthly Windows OS rollup.

Is the Outlook Preview Pane affected?

According to reporting on Microsoft's guidance, the Preview Pane is not an attack vector for this bug — a user has to actually open the crafted message file, not simply preview it in the reading pane.

What's the CISA KEV deadline for this vulnerability?

CISA added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog with a remediation deadline of November 24, 2026 for federal civilian agencies. Private-sector organizations commonly treat KEV deadlines as a practical benchmark even when not legally bound by them.

Sources

More on Patch Tuesday →Patch TuesdayMicrosoft OutlookCVE-2026-124194Windows securityCISA KEV
Sana Qureshi
Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Security & Privacy

See all