Welcome to our

Cyber Security News Aggregator

.

Cyber Tzar

provide a

cyber security risk management

platform; including automated penetration tests and risk assesments culminating in a "cyber risk score" out of 1,000, just like a credit score.

Microsoft Patch Tuesday November 2026: Patch the Outlook zero-day first!

published on 2026-11-11 01:19:16 UTC by Mayuresh
Content:

Microsoft’s November 2026 Patch Tuesday release fixes 1,094 CVEs. Out of those, one is already being exploited: CVE-2026-124194, an Outlook spoofing bug that hands an attacker the user’s NTLMv2 hash when a crafted message file is opened. Saving grace that no other vulnerabilities are publicly disclosed. CISA has already added it to KEV, due 24 November, with no forensic triage. My advice – patch Outlook first, administrators’ machines within three days, and block outbound SMB today. In these series, I rank by the four BOD 26-04 risk variables (KEV status, exposure, automation, technical impact), not by CVSS, because 1,094 CVEs sorted by score bury the one that is being used. KEV values come from catalogVersion 2026.11.10, released 2026-11-10T19:03:29Z, the day Microsoft published. Last updated 2026-11-10.

Microsoft’s release note says 1,094 CVEs, but the CVRF carries 1,095 Microsoft-numbered entries. The odd one out is CVE-2026-122518, the only Microsoft-numbered Microsoft Edge (Chromium-based) entry in the file: an information disclosure bug (CWE-125, CVSS 6.5, network, no privileges, user interaction required) that Microsoft rates Moderate and Exploitation Less Likely, and that could potentially read small portions of heap memory. Its revision history is dated 4 November, six days before the release. My reading is that the note’s count leaves the Edge entry out; Microsoft does not say so. This post includes it, so the first table below totals 1,095, one more than Microsoft’s headline.

Microsoft Patch Tuesday November 2026

Which Microsoft CVEs are exploited or publicly disclosed in November 2026?

CVEComponentTypeCWECVSSExploitabilityKEVDueForensic triage
CVE-2026-124194Outlook (Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024)Spoofing (NTLMv2 hash disclosure)CWE-3566.5DetectedYes, added 2026-11-10 (catalogVersion 2026.11.10)2026-11-24No

Microsoft marks one CVE Exploitation Detected and none publicly disclosed. Its FAQ says an attacker sends a crafted message file and convinces the user to open it; Outlook then connects to an attacker-controlled network location without the usual external-content warning and discloses the user’s NTLMv2 hash, which the attacker can use to authenticate as that user. The Preview Pane is not an attack vector this time. Two details in the record do not line up: the severity is Moderate and the CVSS vector carries E:U (exploit code maturity unproven) while the exploitation flag says Detected. CISA listed it on release day, with a 14-day due date and no forensic-triage requirement.

What should you patch first under BOD 26-04?

CISA added CVE-2026-124194 to KEV on 10 November with a 24 November due date and forensic triage not required: the 14-day tier, not the three-day one. In October, CISA gave a user-interaction Windows Shell bug three days and forensic triage, so user interaction alone does not decide it. The KEV entry gives no reasoning, so I do not know what separated the two. The CISA-ADP SSVC values were not in my data, so the other variables below are my calls and labelled as such. I add one override: a leaked hash from an administrator’s Outlook is a privileged credential, so those machines get three days. The second case is the exposure override: an unauthenticated LDAP bug with no exploitation that the model puts at about 14 days, and that I would patch on domain controllers in three.

CVE-2026-124194, Outlook, spoofing (NTLMv2 hash leak)

  • Exploitation: Detected (MSRC) high: KEV: YES, added 2026-11-10, due 2026-11-24 (CISA catalogVersion 2026.11.10) low: Forensic triage: NO (CISA) low: Technical impact: PARTIAL, a credential and not code execution, my call low: Automatable: NO, the user must open a file, my call high: Exposure: YES, every mailbox accepts mail from the internet, my call outcome: Exploited, on KEV and reachable by any email, but partial impact (my call) and a click required. CISA's 14 days stands for most users. A stolen NTLMv2 hash is a relay or cracking target, so the blast radius is whatever that user can reach; on administrators' machines that is the domain.

CISA: 14 days, due 2026-11-24, no forensic triage

Do: patch Outlook by 2026-11-24, administrators within 3 days; block outbound TCP 445 and 139 today

CVE-2026-119958, Windows LDAP, remote code execution (domain controllers)

  • KEV: NO (CISA catalogVersion 2026.11.10) high: Technical impact: TOTAL, code execution in the LDAP service, my call mid: Automatable: likely YES, unauthenticated LDAP calls, no public exploit, my call low: Exposure: NO, domain controllers should not face the internet, my call outcome: CVSS 9.8, no login, no click, Exploitation Less Likely. Any foothold inside the network reaches LDAP on every domain controller, and code in that service is code on the identity tier. That is why I override the model on these hosts.

Model: about 14 days (not exploited, not exposed)

Do: patch domain controllers within 3 days (tier-0 override)

KEV values from CISA catalogVersion 2026.11.10 (released 2026-11-10T19:03:29Z); exploitation flags from the MSRC CVRF 2026-Nov. CISA-ADP SSVC was not available to me, so automation, impact and exposure are my calls and labelled as such.

Which other CVEs need attention this month?

CVEProductCVSSCWESeverityExploitabilityTier
CVE-2026-116928Windows Search (reached through Exchange attachment indexing)9.8CWE-787CriticalLess LikelyModel: Tier 3, about 14 days. Exchange servers within 7 days, my call
CVE-2026-119958Windows LDAP9.8CWE-787CriticalLess LikelyModel: Tier 3. Domain controllers within 3 days (override)
CVE-2026-118207Exchange Server Subscription Edition8.8CWE-706CriticalMore LikelyModel: Tier 4. Within 14 days, my call (More Likely, low-privilege login)
CVE-2026-118146Active Directory Domain Services8.8CWE-863CriticalMore LikelyModel: Tier 4. Domain controllers within 14 days, my call
CVE-2026-119952Windows Schannel8.1CWE-208CriticalMore LikelyModel: Tier 3, about 14 days
CVE-2026-113862Windows NAT8.1CWE-416CriticalMore LikelyModel: Tier 3, about 14 days on hosts that run NAT
CVE-2026-109459Message Queuing Queue Manager8.1CWE-122CriticalLess LikelyModel: Tier 3 where TCP 1801 is reachable
CVE-2026-112967Xbox Live Networking Service9.8CWE-122CriticalLess LikelyModel: Tier 3, about 14 days
CVE-2026-110043Outlook (Preview Pane is an attack vector)8.8CWE-122CriticalLess LikelyModel: Tier 4. Ships with the Outlook update above
CVE-2026-121663Visual Studio Code8.8CWE-184ImportantMore LikelyModel: Tier 4. Developer machines within 14 days, my call
CVE-2026-121662Visual Studio Code8.6CWE-77ImportantMore LikelyModel: Tier 4. Same update as CVE-2026-121663
CVE-2026-96077Windows TCP/IP (denial of service)7.5CWE-476ImportantMore LikelyModel: Tier 4, about 60 days
CVE-2026-109469Entra Device Registration10.0CWE-639CriticalLess LikelyNone: Microsoft says it is fully mitigated, no customer action
CVE-2026-119990Azure OpenAI9.8CWE-306CriticalN/AMicrosoft says customer action is required but publishes no steps; I do not know what they are

15 CVEs score 9.8 or more with no login and no click. None is exploited.

  • max=15 red: MSRC Critical: 5Entra, Xbox Live Networking, Windows Search, LDAP, Azure OpenAI grey: MSRC Important = 10 group: max=10 dark+bold: The exploited one = 6.5 | CVE-2026-124194, Outlook

Network, no privileges, no user interaction, CVSS 9.8 or 10.0, by MSRC severity. The bottom bar is the only exploited CVE this month.

CVSS and exploitability from the MSRC CVRF 2026-Nov, Microsoft CNA entries only.

How many of these vulnerabilities are reachable without authentication?

The CVSS vector Microsoft publishes as the CNA (privileges required, attack vector, user interaction) and Microsoft’s Exploitability Index for the latest software release. The index is Microsoft’s forecast, not evidence of exploitation, and cloud-service CVEs usually carry N/A. Counts are over all 1,095 Microsoft-numbered CVEs in the CVRF, including the Edge entry CVE-2026-122518.

Privileges requiredDetectedMore LikelyLess LikelyUnlikelyN/ATotal
None (PR:N)15370234403
Low (PR:L)037558309634
High (PR:H)00445049
No CVSS vector008019
Total14298058141095

403 CVEs need no privileges, but only six of them are Detected or More Likely. Of the 42 More Likely flags, 37 sit on bugs that need a login first (PR:L), mostly elevation of privilege. Microsoft expects attackers to use what they already have, not to walk in.

Attack vectorNo UI (UI:N)UI required (UI:R)Total
Network (AV:N)88252340
Adjacent (AV:A)15015
Local (AV:L)12223
Physical (AV:P)24125
Total128275403

88 CVEs are reachable over the network with no login and no click. That is the list to check against your exposure inventory, not the 1,095.

TypeMore LikelyLess LikelyUnlikelyN/ATotal
Remote Code Execution2291032
Elevation of Privilege06028
Information Disclosure0120012
Denial of Service1260027
Security Feature Bypass05005
Spoofing03014
Total3811388

Of those 88, 32 are remote code execution and two are More Likely. Sixteen are Critical, 14 are Critical remote code execution, 15 score 9.8 or more, and none of the 15 is More Likely. A 9.8 is a severity, not a forecast.

CVETitleCVSSVectorSeverityExploitability
CVE-2026-124194Microsoft Outlook Spoofing Vulnerability6.5AV:N/AC:L/PR:N/UI:R/S:UModerateDetected
CVE-2026-121663Visual Studio Code Security Feature Bypass Vulnerability8.8AV:N/AC:L/PR:N/UI:R/S:UImportantMore Likely
CVE-2026-121662Visual Studio Code Remote Code Execution Vulnerability8.6AV:L/AC:L/PR:N/UI:R/S:CImportantMore Likely
CVE-2026-113862Windows Network Address Translation (NAT) Remote Code Execution Vulnerability8.1AV:N/AC:H/PR:N/UI:N/S:UCriticalMore Likely
CVE-2026-119952Windows Schannel Remote Code Execution Vulnerability8.1AV:N/AC:H/PR:N/UI:N/S:UCriticalMore Likely
CVE-2026-96077Windows TCP/IP Denial of Service Vulnerability7.5AV:N/AC:L/PR:N/UI:N/S:UImportantMore Likely

How do you detect exploitation of these CVEs?

Lead with the gap: a hash leak has no exploit on the endpoint to catch. What you see is the network outcome, an SMB or WebDAV connection to an address you do not own, and later the attacker using the hash. Memory-corruption bugs in LDAP, Search and MSMQ give little signal before exploitation, so the hunts below look for crashes and for services starting things they never start. Microsoft documents no workaround or mitigation for CVE-2026-124194 in the CVRF; the update is the fix. The Sysmon overlay that feeds these rules is PatchTuesday-2026-11.xml, include-only, to merge into your baseline.

CVECWEATT&CKHuntRule
CVE-2026-124194CWE-356T1187Sysmon EID 3 from System (the kernel SMB client) or OUTLOOK.EXE to TCP 445 or 139 on a public address; firewall denies for the same flow; EID 1 rundll32 davclnt.dll,DavSetCookie for the WebDAV fallback; then NTLM logons (4624, type 3) for that user from addresses you do not knowSMB to a public IP (new); SigmaHQ 982e9f2d
CVE-2026-116928CWE-787T1190, T1203Sysmon EID 1 on Exchange servers: any child of SearchIndexer.exe, SearchProtocolHost.exe or SearchFilterHost.exe other than the Search hosts, WerFault or conhost; WerFault started by those processes (crash after a failed attempt)Search child (new); Search or IIS crash (new)
CVE-2026-119958CWE-787T1210LDAP runs in LSASS: Application event 1000 for lsass.exe and WerFault started by lsass.exe on domain controllers; a domain controller rebooting on its own is the loud versioncritical service crash (October); SigmaHQ a18e0862
CVE-2026-118146CWE-863T1210AD DS runs in LSASS: Application event 1000 for lsass.exe and WerFault started by lsass.exe on domain controllers; a domain controller rebooting on its own is the loud versioncritical service crash (October); SigmaHQ a18e0862
CVE-2026-119952CWE-208T1210Schannel runs in LSASS: Application event 1000 for lsass.exe and WerFault started by lsass.exe on domain controllers; a domain controller rebooting on its own is the loud versioncritical service crash (October); SigmaHQ a18e0862
CVE-2026-109459CWE-122T1210Sysmon EID 1 children of mqsvc.exe; EID 3 peers of mqsvc.exe on TCP 1801 that are not expected sendersSigmaHQ 53207cc2
CVE-2026-118207CWE-706T1190Script files written under the Exchange web directories; shells started by Exchange worker processesExchange web directory script write (October)
CVE-2026-121662CWE-77T1204.002Sysmon EID 1 children of Code.exe running script hosts, LOLBins or download cradles, after a workspace from a clone or download is openedSigmaHQ 5a3164f2
CVE-2026-121663CWE-184T1204.002Sysmon EID 1 children of Code.exe running script hosts, LOLBins or download cradles, after a workspace from a clone or download is openedSigmaHQ 5a3164f2
CVE-2026-110043CWE-122T1203Sysmon EID 1 children of OUTLOOK.EXE (shells, script hosts, LOLBins)SigmaHQ 208748f7

My key takeaways

  • Patch Outlook by CISA’s 24 November due date, administrators’ machines first, and block outbound SMB at the edge today. The block also covers the next forced-authentication bug, and CVE-2026-124194 will not be the last.
  • Patch the Exchange servers’ Windows build, not only Exchange. CVE-2026-116928 lives in Windows Search and is reached by mail alone.
  • Domain controllers get three days for CVE-2026-119958 regardless of the model. No exploitation is reported; the asset decides the deadline.
  • Do not rank by the 9.8s. Fifteen zero-click CVEs score 9.8 or more and none is forecast as likely to be exploited, while the one being used scores 6.5 and is rated Moderate.
  • Treat CVE-2026-109469 (Entra, CVSS 10.0) as a transparency record and not a task. Microsoft fixed it in the service.

What did government CERTs say about the November 2026 release?

4 government CERTs had published a notice by 2026-11-11. MSRC and CISA KEV stay the source of record for every value in this post. This table shows what each national team told its readers, and where that differs.

CERTNoticePublishedRatingCVEs ListedInformation
CCB (Belgium)Warning: Microsoft Patch Tuesday November 2026Not shownNone statedNot readHeadline gives 1,093 vulnerabilities: 63 Critical, 1,029 Important, 1 Moderate (page did not load; title read from CCB’s own URL and search listing)
CISA (United States)KEV alert 2026-11-102026-11-10None stated1; exploited: CVE-2026-124194Adds the Outlook CVE to KEV, due 2026-11-24 (alert page did not load here; values from KEV catalogVersion 2026.11.10)
Canadian Centre for Cyber Security (Canada)AV26-1142 [Likely]2026-11-10None stated1; exploited: CVE-2026-124194‘Microsoft indicates that CVE-2026-124194 has been exploited’; lists affected products and says apply updates
NCSC-NL (Netherlands)NCSC-2026-04722026-11-10Kans medium, Schade high13Windows fixes; lists its 13 most serious (CVSS 9.0 or higher); no exploitation stated
NCSC-NL (Netherlands)NCSC-2026-04732026-11-10Kans medium, Schade high12Developer tools fixes; no exploitation stated (CVE list read in part)
NCSC-NL (Netherlands)NCSC-2026-04742026-11-10Kans medium, Schade high3Office fixes, led by two SharePoint CVEs; lists CVE-2026-124194 in its Outlook table as spoofing, CVSS 6.5, with no word on exploitation
NCSC-NL (Netherlands)NCSC-2026-04752026-11-10Kans medium, Schade high19Azure fixes, led by CVE-2026-119990; no exploitation stated
NCSC-NL (Netherlands)NCSC-2026-04762026-11-10Kans medium, Schade high155 SQL Server fixes, led by CVE-2026-116945; no exploitation stated (CVE list read in part)
NCSC-NL (Netherlands)NCSC-2026-04772026-11-10Kans medium, Schade high99 Exchange Server fixes; no exploitation stated
CSA / SingCERT (Singapore)AL-2026-1602026-11-11Critical68Lists 68 CVEs (four of them Chrome-numbered) as ‘Critical in severity’; names no exploited CVE; links the MSRC release note
HKCERT (Hong Kong)Microsoft Monthly Security Update (November 2026)2026-11-11Medium Risk1; exploited: CVE-2026-124194Rates all 14 product groups Medium Risk; says CVE-2026-124194 is exploited in the wild and needs user interaction; apply the fixes
INCIBE-CERT (Spain)Boletín de seguridad de Microsoft de noviembre de 2026 [Likely]2026-11-1123 críticas, 1 media24; exploited: CVE-2026-124194‘Microsoft confirma que esta vulnerabilidad está siendo explotada activamente’ for CVE-2026-124194; lists 23 critical CVEs plus the Outlook one
JPCERT/CC (Japan)JPCERT-AT-2026-00352026-11-11None stated1; exploited: CVE-2026-124194Says CVE-2026-124194 ‘has been confirmed to be exploited in the wild’; install the November updates

Checked, nothing found as of 2026-11-17: ASD’s ACSC, BSI / CERT-Bund, CERT Polska, CERT-EU, CERT-FR, CERT-In, CERT-RS (RATEL), CERT.at, CERTuy, CIRCL Vulnerability-Lookup, ENISA EUVD, KrCERT/CC (KISA), NCA (Saudi CERT), NCSC NZ (CERT NZ), NCSC UK, NCSC-FI (Traficom), NKI.

Frequently asked questions

How many CVEs did Microsoft fix in November 2026 Patch Tuesday?

Microsoft’s November 2026 release note lists 1,094 CVEs. The public CVRF carries 1,095 Microsoft-numbered entries; the extra one, CVE-2026-122518, the only Microsoft-numbered Microsoft Edge (Chromium-based) entry, is an information disclosure bug rated Moderate. One CVE is exploited and none is publicly disclosed.

Which November 2026 Patch Tuesday CVE should I patch first?

Patch CVE-2026-124194, the Outlook spoofing bug Microsoft marks Exploitation Detected, by CISA’s 24 November due date, administrators’ machines within three days, and block outbound TCP 445 and 139 now. Then patch domain controllers for CVE-2026-119958 (LDAP, CVSS 9.8) and the Windows build on Exchange servers for CVE-2026-116928.

Are any November 2026 Patch Tuesday vulnerabilities exploited in the wild?

Yes, one: Microsoft marks CVE-2026-124194 in Outlook as Exploitation Detected. CISA added it to KEV on 10 November (catalogVersion 2026.11.10) with a 24 November due date under BOD 26-04 and no forensic-triage requirement.

Can CVE-2026-116928 be exploited without anyone opening an email?

Yes, according to Microsoft, an unauthenticated attacker sends an email with a crafted attachment, Exchange indexes it automatically through the Windows Search component, and the recipient does not need to open anything. It scores 9.8 and is rated “Exploitation Less Likely”.

Article: Microsoft Patch Tuesday November 2026: Patch the Outlook zero-day first! - published 11 days ago.

https://pentestit.com/microsoft-patch-tuesday-november-2026-exploitability-and-patching-priority/   
Published: 2026 11 11 01:19:16
Received: 2026 11 20 07:48:30
Feed: PenTestIT
Source: PenTestIT
Category: News
Topic: Security Tooling
Views: 1

Custom HTML Block

Click to Open Code Editor