This website uses cookies

Read our Privacy policy and Terms of use for more information.

Microsoft's November 2026 release fixes 1,097 vulnerabilities, 64 of them rated Critical. Of those, one is already exploited in the wild.

Start November’s patch cycle with Outlook: an actively exploited spoofing flaw can suppress the usual external-content warning and potentially expose authentication information when a user opens a crafted message file.

Mariner also needs urgent attention because of its CISA KEV listing. Beyond those two, the patching priorities span server-side code execution in Exchange and Active Directory, plus Visual Studio Code flaws that can let a malicious workspace execute code without the user granting trust.

Patch these first

  • CVE-2026-124194 (Moderate, CVSS 6.5) — Microsoft Office Outlook: Spoofing — exploited in the wild, CISA KEV

  • CVE-2026-123158 (Important, CVSS 8.1) — Mariner: see advisory — CISA KEV

CVE-2026-124194 affects Microsoft Office Outlook and is both actively exploited and listed in CISA KEV. An unauthenticated attacker can send a specially crafted message file and persuade a user to open it; Outlook may then connect to an attacker-controlled network location without its usual external-content warning. That connection could disclose authentication information usable to impersonate the user. Exploitation requires user interaction and network connectivity, but the missing warning removes a safeguard at the point of opening. Prioritize the Outlook update on affected installations.

CVE-2026-123158 is the Mariner entry in CISA KEV. That known-exploited status makes it an urgent patching task for organizations running affected Mariner systems. Apply the customer-side update rather than deferring it behind the broader November rollout.

Also notable

  • CVE-2026-118207 (Critical, CVSS 8.8) — Microsoft Exchange Server: Remote Code Execution

  • CVE-2026-118146 (Critical, CVSS 8.8) — Active Directory Domain Services: Remote Code Execution

  • CVE-2026-121663 (Important, CVSS 8.8) — Visual Studio Code: Security Feature Bypass

  • CVE-2026-121662 (Important, CVSS 8.6) — Visual Studio Code: Remote Code Execution

  • CVE-2026-113862 (Critical, CVSS 8.1) — Windows Network Address Translation (NAT): Remote Code Execution

  • CVE-2026-119952 (Critical, CVSS 8.1) — Windows Schannel: Remote Code Execution

  • CVE-2026-118148 (Critical, CVSS 7.5) — Active Directory Domain Services: Elevation of Privilege

  • CVE-2026-119958 (Critical, CVSS 9.8) — Windows LDAP - Lightweight Directory Access Protocol: Remote Code Execution

For server teams, Exchange Server’s CVE-2026-118207 and Active Directory Domain Services’ CVE-2026-118146 share an important attack prerequisite: an authenticated attacker with low-level access can send a crafted request and execute code on the affected server without user interaction. Both are rated exploitation more likely. Windows LDAP’s CVE-2026-119958 removes the authentication prerequisite: crafted LDAP calls can produce arbitrary code execution in the LDAP service’s context, although Microsoft rates exploitation less likely. These are customer-side patching tasks; the distinction between authenticated and unauthenticated access should inform scheduling alongside the exploitation assessments.

Developer workstations also need attention. Visual Studio Code’s CVE-2026-121663 and CVE-2026-121662 can let a specially crafted workspace bypass Workspace Trust protections and execute attacker-controlled content as the user. Opening the workspace requires user interaction, but granting trust does not—a meaningful distinction for developers who rely on that boundary when inspecting unfamiliar workspaces. Both are rated exploitation more likely and require updates.

By the numbers

  • Elevation of Privilege: 536

  • Remote Code Execution: 297

  • Information Disclosure: 157

  • Denial of Service: 46

  • Security Feature Bypass: 27

  • Spoofing: 22

  • Tampering: 11

  • Other: 1

Not counted above: 342 open-source CVEs (mostly Azure Linux packages) that Microsoft republished this month. Azure Linux admins should pick those up through the normal package updates.

Bottom line

Patch affected Outlook installations first: exploitation is already occurring, and opening a crafted message file can expose authentication information without the usual warning. Put Mariner’s KEV-listed fix in the same urgent workstream, then move through the server and developer-tool updates according to their attack prerequisites.

Reply

Avatar

or to participate