Action1 5 Patch Tuesday 5 Patch Tuesday November 2026

Patch Tuesday November 2026

Published:
November 10, 2026
Last Updated:
November 11, 2026

By Jack Bicer

First 200 endpoints free, no feature limits.

No credit card required, full access to all features.

Patch Tuesday November 2026 Updates – Vulnerability Digest from Action1

This digest covers the most serious vulnerabilities patched by Microsoft in this month’s Patch Tuesday release.

For even more information, watch the recorded November 2026 Vulnerability Digest webinar, join our next Patch Tuesday webinar and visit our Patch Tuesday Watch page.

Microsoft Vulnerabilities

Microsoft’s November 2026 Patch Tuesday delivers another exceptionally large update cycle, with 1,094 patches, including 63 critical vulnerabilities and one zero-day, CVE-2026-124194. While that is down from October’s record-breaking 1,409 patches, it still marks the third consecutive month with patch volumes at levels that would have been extraordinary earlier this year.

This month’s zero-day gives IT and security teams an obvious starting point, but the broader challenge remains prioritization across a release of more than a thousand patches. Teams will need to weigh severity, exploitability, affected systems, and business exposure to determine what should move first.

As AI accelerates vulnerability discovery and exploitation, no software vendor can guarantee its platform will never be compromised. Action1 pioneered Endpoint Takeover Prevention (ETP) to protect endpoints even if the management platform is compromised. We’re inviting fellow endpoint management vendors to explore our architecture, exchange insights, and help bring takeover-resilient security to the wider industry.

Below, we break down the November updates and highlight the vulnerabilities that deserve the closest attention.

[1] Zero-Day – Immediate Deployment CVE-2026-124194 – Microsoft Outlook Spoofing Vulnerability

“No warning, no alarm. One message file, one click, and your password hash is already on its way to an attacker.”

CVE-2026-124194 is a spoofing flaw in Microsoft Outlook that attackers are already using. An attacker sends a specially crafted message file and gets the user to open it. Outlook then connects to a network location the attacker controls, but it skips the usual warning about external content. That quiet connection can leak the user's NTLMv2 hash, a scrambled form of their login secret, which the attacker can use to sign in as that person. It affects Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024.

CVSS Score: 6.5

SEVERITY: Moderate

THREAT: An attacker with no account could trick a user into opening a crafted message file and steal that user's NTLMv2 hash. With it, they could sign in as the user and reach what that person can reach.

EXPLOITS: This vulnerability is actively exploited. The issue was not publicly disclosed before the fix, and no confirmed public proof-of-concept is identified.

TECHNICAL SUMMARY: The root cause is CWE-356: the product interface does not warn the user about an unsafe action. When Outlook opens a crafted message file, it reaches out to an attacker-controlled network location without showing the normal external-content warning. During that connection, Windows sends the user's NTLMv2 authentication data, and the attacker captures the hash. The attacker can then use it to authenticate as the user. The CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. The attack works over the network, is easy to carry out, and needs no privileges, but the user must open the file. The impact is a high loss of confidentiality, with no direct effect on integrity or availability. The Preview Pane is not an attack vector.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit) and Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit). The fix ships as a security update through the Office release channels. An attacker sends a malicious Office message file and convinces the user to open it in Outlook.

BUSINESS IMPACT: Email is the easiest door into any company, and this flaw turns one opened file into stolen identity. A captured hash can let an attacker sign in as the victim, read their data, and move to other systems they can reach. If the victim is an administrator or a finance user, the damage grows fast. Because the warning users are trained to watch for never appears, even careful staff can be caught. Attackers are already using it, so this is a live risk, not a theory.

WORKAROUND: No official mitigations or workarounds are listed. Until the update is in place, warn users not to open unexpected message files, block outbound SMB traffic (TCP 445) to the internet, and watch for unusual sign-ins that may use stolen hashes.

URGENCY: The Moderate label undersells this one. Attackers are already exploiting it, it needs only one click on an email file, and it hits Outlook, which nearly every organization runs. A stolen hash can open doors far beyond the inbox. Push the Office update to every Outlook user now, starting with administrators and high-value accounts.

SPEAKER NOTES:

  • Attackers are actively exploiting this Outlook spoofing flaw.
  • Opening a crafted message file makes Outlook connect out with no warning.
  • That connection can leak the user's NTLMv2 hash, which lets attackers sign in as them.
  • The Preview Pane is not an attack path, so the user must open the file.
  • Deploy the Office update to all Outlook users right away, even though it is rated Moderate.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-120003 – Microsoft Office Remote Code Execution Vulnerability

“One bad file, one overflow, and the attacker is running code on your desktop. Office stays the front door attackers love to knock on.”

This is a heap-based buffer overflow in Microsoft Office. An attacker can craft a malicious file that, when the user interacts with it, writes past the end of a memory buffer and lets the attacker run code with the user's permissions. The attacker needs no privileges on the target. Microsoft rates it Critical.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: A remote attacker could trick a user into handling a malicious Office file and then run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-122, Heap-based Buffer Overflow. Office copies data into a heap buffer without making sure it fits, so a crafted file can overwrite nearby memory and take control of execution. The CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: network, low complexity, no privileges, user interaction required, with high impact. Microsoft has not published additional FAQ details on the exact trigger, so the precise file type and user action cannot be confirmed from the data.

EXPLOITABILITY: Affected: Microsoft 365 Apps for Enterprise (32-bit and 64-bit) and Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit). Fixes are delivered through the Office release channels. An attacker would deliver a crafted file and rely on the user to interact with it.

BUSINESS IMPACT: Office runs on almost every corporate desktop, and malicious documents remain one of the most common ways attackers get in. Code execution on a single workstation can lead to stolen credentials, data theft, and ransomware that spreads across the network. Users with admin rights make the impact far worse.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, block or quarantine Office attachments from untrusted senders, keep users on least-privilege accounts, and remind staff to be careful with unexpected files.

URGENCY: This flaw is Critical, reachable over the network, and needs no privileges, only a user interacting with a file. Because Office is so widely deployed, the attack surface is enormous. Roll out the Office update across all channels quickly and verify devices are current.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118730 – Microsoft Office Excel Remote Code Execution Vulnerability

Your spreadsheet should crunch numbers, not hand over your computer. Opening one bad workbook could give an attacker the keys to the user's session.

CVE-2026-118730 is a remote code execution flaw in Microsoft Excel caused by a use-after-free memory bug. An attacker who gets a user to open a specially crafted Excel file could run code on that user's computer with the same rights as the user. The flaw affects Microsoft 365 Apps, Office LTSC 2021 and 2024, and Office Online Server.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any outside attacker who can deliver a malicious workbook by email, chat, or file share could take over the victim's session and run code with that user's permissions.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a use-after-free (CWE-416) in Microsoft Excel. Excel releases a piece of memory while handling a workbook but keeps using a stale pointer to it. A crafted file can fill that freed memory with attacker-controlled data, letting the attacker redirect execution and run code. The attack needs no login and no special privileges, but it does require the user to take part: open a specially crafted file sent by the attacker. The Preview Pane is not an attack vector, which removes one easy path for attackers. If the attack works, the attacker gets full control over confidentiality, integrity, and availability within the user's context, which means they can steal data, change files, or install more malware.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit), plus Office Online Server (fixed by update 5002946, which replaces 5002928). To exploit this flaw, an attacker sends or shares a booby-trapped workbook and persuades the user to open a specially crafted Excel file.

BUSINESS IMPACT: Excel sits at the heart of finance, HR, sales, and operations, and spreadsheets are shared all day long. That makes a poisoned workbook an easy and believable lure. One successful attack can give an intruder a foothold on a user's machine, open the door to data theft or ransomware, and spread to shared drives and other systems. The fallout can include downtime, breach costs, regulatory trouble, and lost customer trust.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, block or quarantine Office files from unknown senders, keep Protected View on for files from the internet, use attack surface reduction rules to stop Office apps from launching child processes, and remind users not to open unexpected attachments.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. It needs no credentials, only a user who opens a file, and Excel is installed on almost every business desktop. Spreadsheet lures are one of the most common phishing tricks, so the gap between a fix and real attacks can be short. Deploy the Office update across all affected editions, and Office Online Server where used, as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118713 – Microsoft Office Excel Remote Code Execution Vulnerability

One click into the wrong cell could be all it takes. Editing a booby-trapped workbook can let an attacker run code on the user's machine.

CVE-2026-118713 is a remote code execution flaw in Microsoft Excel caused by a use-after-free memory bug. An attacker who gets a user to open a specially crafted workbook and edit a cell in it could run code on that user's computer with the same rights as the user. The attack is triggered when the user edits a cell in the malicious workbook.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any outside attacker who can deliver a malicious workbook by email, chat, or file share could take over the victim's session and run code with that user's permissions.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a use-after-free (CWE-416) in Microsoft Excel. When the user edits a cell in a crafted workbook, Excel frees memory tied to that data but still references it later. An attacker who controls what lands in that memory can take over the program's flow and run code. The attack needs no login and no special privileges, but it does require the user to take part: the user must open a crafted workbook in an affected version of Excel and edit a cell in it. The Preview Pane is not an attack vector, which removes one easy path for attackers. If the attack works, the attacker gets full control over confidentiality, integrity, and availability within the user's context, which means they can steal data, change files, or install more malware.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit), plus Office Online Server (fixed by update 5002946, which replaces 5002928). To exploit this flaw, an attacker sends or shares a booby-trapped workbook and persuades the user to open a specially crafted workbook and edit a cell in it.

BUSINESS IMPACT: Excel sits at the heart of finance, HR, sales, and operations, and spreadsheets are shared all day long. That makes a poisoned workbook an easy and believable lure. One successful attack can give an intruder a foothold on a user's machine, open the door to data theft or ransomware, and spread to shared drives and other systems. The fallout can include downtime, breach costs, regulatory trouble, and lost customer trust.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, block or quarantine Office files from unknown senders, keep Protected View on for files from the internet, use attack surface reduction rules to stop Office apps from launching child processes, and remind users not to open unexpected attachments.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. It needs no credentials, only a user who opens a file, and Excel is installed on almost every business desktop. Spreadsheet lures are one of the most common phishing tricks, so the gap between a fix and real attacks can be short. Deploy the Office update across all affected editions, and Office Online Server where used, as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118711 – Microsoft Office Excel Remote Code Execution Vulnerability

A single cell edit can overflow into a full compromise. This Excel bug lets a crafted workbook break out of its box and run the attacker's code.

CVE-2026-118711 is a remote code execution flaw in Microsoft Excel caused by a stack-based buffer overflow. An attacker who gets a user to open a specially crafted workbook and edit a cell in it could run code on that user's computer with the same rights as the user. The attack is triggered when the user edits a cell in the malicious workbook.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any outside attacker who can deliver a malicious workbook by email, chat, or file share could take over the victim's session and run code with that user's permissions.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a stack-based buffer overflow (CWE-121) in Microsoft Excel. When a cell in a crafted workbook is edited, Excel copies more data onto the stack than the buffer can hold. The extra data overwrites nearby memory, which an attacker can use to take over execution and run code. The attack needs no login and no special privileges, but it does require the user to take part: the user must open a crafted workbook in an affected version of Excel and edit a cell in it. The Preview Pane is not an attack vector, which removes one easy path for attackers. If the attack works, the attacker gets full control over confidentiality, integrity, and availability within the user's context, which means they can steal data, change files, or install more malware.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit), plus Office Online Server (fixed by update 5002946, which replaces 5002928). To exploit this flaw, an attacker sends or shares a booby-trapped workbook and persuades the user to open a specially crafted workbook and edit a cell in it.

BUSINESS IMPACT: Excel sits at the heart of finance, HR, sales, and operations, and spreadsheets are shared all day long. That makes a poisoned workbook an easy and believable lure. One successful attack can give an intruder a foothold on a user's machine, open the door to data theft or ransomware, and spread to shared drives and other systems. The fallout can include downtime, breach costs, regulatory trouble, and lost customer trust.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, block or quarantine Office files from unknown senders, keep Protected View on for files from the internet, use attack surface reduction rules to stop Office apps from launching child processes, and remind users not to open unexpected attachments.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. It needs no credentials, only a user who opens a file, and Excel is installed on almost every business desktop. Spreadsheet lures are one of the most common phishing tricks, so the gap between a fix and real attacks can be short. Deploy the Office update across all affected editions, and Office Online Server where used, as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118702 – Microsoft Office Excel Remote Code Execution Vulnerability

Open the file, lose the machine: a memory bug in Excel could let attackers run code through a single crafted spreadsheet.

CVE-2026-118702 is a Critical remote code execution vulnerability in Microsoft Office Excel caused by a double free memory error. An attacker who convinces a user to open a specially crafted file could run code on the computer with the user's rights. The Preview Pane is not an attack vector, so the file must actually be opened. Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024 are affected.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated attacker who tricks a user into opening a malicious workbook could run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is a double free (CWE-415) in Microsoft Office Excel. When Excel processes a specially crafted file, it can release the same block of memory twice. That corrupts the heap and can let an attacker control program flow and run their own code in the context of the user. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: the malicious file is delivered over the network, the attack is low in complexity and needs no privileges, but the user must open the file. The Preview Pane is not an attack vector. A successful attack has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Microsoft 365 Apps for Enterprise (32-bit and 64-bit) and Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit editions) are affected. An attacker must get a user to open a specially crafted file, usually through email or a download. Simply previewing the file in the Preview Pane does not trigger the bug.

BUSINESS IMPACT: Excel sits on nearly every business desktop, and spreadsheets are among the most trusted files people open every day. A single opened invoice, report, or budget file could give an attacker a foothold on a workstation, with access to the user's email, documents, and saved credentials. From there, attackers can steal data, install ransomware, or move deeper into the network. Finance, HR, and executive teams, who handle spreadsheets constantly, are prime targets.

WORKAROUND: No official mitigation or workaround is listed, so patching is the real fix. Until then, tell users not to open Excel files from unknown or unexpected senders, keep Protected View on for files from the internet and email, and filter or block risky spreadsheet attachments at the mail gateway.

URGENCY: This is rated Critical with a CVSS score of 8.8, needs no privileges, and targets one of the most widely used business applications. The only hurdle is getting a user to open a file, which phishing attackers clear every day. No exploitation has been seen yet, but Microsoft 365 Apps and Office LTSC should be updated in this patch cycle.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118701 – Microsoft Office Excel Remote Code Execution Vulnerability

Open it, save it, and you may have just handed over your computer: this Excel bug turns everyday file habits into risk.

CVE-2026-118701 is a Critical remote code execution vulnerability in Microsoft Office Excel caused by a heap-based buffer overflow. An attacker could convince a user to open a specially crafted workbook in an affected version of Excel and save it, which could let the attacker run code with the user's privileges. The Preview Pane is not an attack vector. Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024, and Office Online Server are affected.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated attacker who tricks a user into opening a malicious workbook could run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Microsoft Office Excel. When a user opens a specially crafted workbook and then saves it, Excel can write data past the end of a heap buffer. An attacker who controls that overflow can corrupt memory and run code with the user's privileges. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: network delivery, low complexity, no privileges, but user interaction is required. The Preview Pane is not an attack vector. A successful attack has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit editions), and Office Online Server (fixed by update 5002946) are affected. An attacker must convince a user to open a specially crafted workbook in an affected version of Excel and save it. Previewing the file is not enough to trigger the bug.

BUSINESS IMPACT: Excel sits on nearly every business desktop, and spreadsheets are among the most trusted files people open every day. A single opened invoice, report, or budget file could give an attacker a foothold on a workstation, with access to the user's email, documents, and saved credentials. From there, attackers can steal data, install ransomware, or move deeper into the network. Finance, HR, and executive teams, who handle spreadsheets constantly, are prime targets.

WORKAROUND: No official mitigation or workaround is listed, so patching is the real fix. Until then, tell users not to open Excel files from unknown or unexpected senders, keep Protected View on for files from the internet and email, and filter or block risky spreadsheet attachments at the mail gateway.

URGENCY: This is rated Critical with a CVSS score of 8.8, needs no privileges, and targets one of the most widely used business applications in the world. The attack path is simple and familiar: send a file, get it opened. Even though no exploitation has been seen yet, Excel file bugs are a favorite phishing tool, so update Microsoft 365 Apps, Office LTSC, and Office Online Server in this patch cycle.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118297 – Microsoft Office Excel Remote Code Execution Vulnerability

The most dangerous spreadsheet is the one that looks completely normal. One crafted Excel file could quietly turn a routine task into a full system compromise.

CVE-2026-118297 is a remote code execution flaw in Microsoft Excel caused by a heap-based buffer overflow. An attacker who gets a user to open a specially crafted Excel file could run code on that user's computer with the same rights as the user. The flaw affects Microsoft 365 Apps, Office LTSC 2021 and 2024, and Office Online Server.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any outside attacker who can deliver a malicious workbook by email, chat, or file share could take over the victim's session and run code with that user's permissions.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Microsoft Excel. While parsing a crafted file, Excel writes more data into a heap buffer than it was sized for. That overflow corrupts nearby heap memory, which an attacker can shape to take control of execution and run code. The attack needs no login and no special privileges, but it does require the user to take part: the user must open a specially crafted file sent by the attacker. The Preview Pane is not an attack vector, which removes one easy path for attackers. If the attack works, the attacker gets full control over confidentiality, integrity, and availability within the user's context, which means they can steal data, change files, or install more malware.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit), plus Office Online Server (fixed by update 5002946, which replaces 5002928). To exploit this flaw, an attacker sends or shares a booby-trapped workbook and persuades the user to open a specially crafted Excel file.

BUSINESS IMPACT: Excel sits at the heart of finance, HR, sales, and operations, and spreadsheets are shared all day long. That makes a poisoned workbook an easy and believable lure. One successful attack can give an intruder a foothold on a user's machine, open the door to data theft or ransomware, and spread to shared drives and other systems. The fallout can include downtime, breach costs, regulatory trouble, and lost customer trust.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, block or quarantine Office files from unknown senders, keep Protected View on for files from the internet, use attack surface reduction rules to stop Office apps from launching child processes, and remind users not to open unexpected attachments.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. It needs no credentials, only a user who opens a file, and Excel is installed on almost every business desktop. Spreadsheet lures are one of the most common phishing tricks, so the gap between a fix and real attacks can be short. Deploy the Office update across all affected editions, and Office Online Server where used, as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118296 – Microsoft Office Excel Remote Code Execution Vulnerability

Freeing memory twice is a mistake attackers love. One malicious workbook could use this Excel bug to run code with the user's full rights.

CVE-2026-118296 is a remote code execution flaw in Microsoft Excel caused by a double free memory bug. An attacker who gets a user to open a specially crafted Excel file could run code on that user's computer with the same rights as the user. The flaw affects Microsoft 365 Apps, Office LTSC 2021 and 2024, and Office Online Server.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any outside attacker who can deliver a malicious workbook by email, chat, or file share could take over the victim's session and run code with that user's permissions.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a double free (CWE-415) in Microsoft Excel. While processing a crafted file, Excel releases the same block of memory twice. That corrupts the memory manager's internal state, and an attacker can use the corruption to take control of execution and run code. The attack needs no login and no special privileges, but it does require the user to take part: the user must open a specially crafted file sent by the attacker. If the attack works, the attacker gets full control over confidentiality, integrity, and availability within the user's context, which means they can steal data, change files, or install more malware.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit), plus Office Online Server (fixed by update 5002946, which replaces 5002928). To exploit this flaw, an attacker sends or shares a booby-trapped workbook and persuades the user to open a specially crafted Excel file.

BUSINESS IMPACT: Excel sits at the heart of finance, HR, sales, and operations, and spreadsheets are shared all day long. That makes a poisoned workbook an easy and believable lure. One successful attack can give an intruder a foothold on a user's machine, open the door to data theft or ransomware, and spread to shared drives and other systems. The fallout can include downtime, breach costs, regulatory trouble, and lost customer trust.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, block or quarantine Office files from unknown senders, keep Protected View on for files from the internet, use attack surface reduction rules to stop Office apps from launching child processes, and remind users not to open unexpected attachments.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. It needs no credentials, only a user who opens a file, and Excel is installed on almost every business desktop. Spreadsheet lures are one of the most common phishing tricks, so the gap between a fix and real attacks can be short. Deploy the Office update across all affected editions, and Office Online Server where used, as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118148 – Active Directory Domain Services Elevation of Privilege Vulnerability

“Win a race, gain SYSTEM. When Active Directory falls, the whole kingdom falls with it.”

CVE-2026-118148 is an incorrect authorization flaw in Active Directory Domain Services. An attacker with a low-privileged account can exploit it over the network to gain SYSTEM privileges. The attack is complex because the attacker must win a race condition, but successful exploitation is considered more likely.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An authenticated attacker with low-level access could gain SYSTEM privileges on an affected system, opening the door to domain-wide compromise.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is incorrect authorization (CWE-863) in Active Directory Domain Services. Under certain timing, the service fails to enforce the right access checks, so a low-privileged user can perform actions they should not be allowed to. The attacker must win a race condition to exploit it. The attack is over the network, with high complexity, low privileges, and no user interaction. A successful attacker gains SYSTEM privileges, with high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. An attacker with valid low-privileged credentials sends requests over the network and races the authorization check to escalate.

BUSINESS IMPACT: Active Directory controls who can access what across the business. SYSTEM access on a domain controller can lead to control of every account, server, and workstation in the domain. That means mass ransomware deployment, data theft, and a long, costly recovery.

WORKAROUND: No official workarounds are listed. Limit who can log on to domain controllers, monitor for unusual directory activity, and enforce strong account hygiene until the patch is applied.

URGENCY: This is a Critical bug in the heart of most corporate networks, and exploitation is considered more likely. Any user account could be the starting point. Patch domain controllers first, then the rest of the fleet.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118292 – Microsoft Office Excel Remote Code Execution Vulnerability

Even a simple 'Save As' can turn dangerous. This Excel flaw lets a crafted workbook hijack the save process and run the attacker's code.

CVE-2026-118292 is a remote code execution flaw in Microsoft Excel caused by a stack-based buffer overflow. An attacker who gets a user to open a specially crafted workbook and save it in a different file format could run code on that user's computer with the same rights as the user. The attack is triggered when the user saves the malicious workbook in a different file format.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any outside attacker who can deliver a malicious workbook by email, chat, or file share could take over the victim's session and run code with that user's permissions.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a stack-based buffer overflow (CWE-121) in Microsoft Excel. When a crafted workbook is saved in a different file format, Excel copies data onto the stack without checking its size. The overflow overwrites nearby memory, which an attacker can use to take over execution and run code. The attack needs no login and no special privileges, but it does require the user to take part: the user must open a crafted workbook in an affected version of Excel and save it in a different file format. The Preview Pane is not an attack vector, which removes one easy path for attackers. If the attack works, the attacker gets full control over confidentiality, integrity, and availability within the user's context, which means they can steal data, change files, or install more malware.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit), plus Office Online Server (fixed by update 5002946, which replaces 5002928). To exploit this flaw, an attacker sends or shares a booby-trapped workbook and persuades the user to open a specially crafted workbook and save it in a different file format.

BUSINESS IMPACT: Excel sits at the heart of finance, HR, sales, and operations, and spreadsheets are shared all day long. That makes a poisoned workbook an easy and believable lure. One successful attack can give an intruder a foothold on a user's machine, open the door to data theft or ransomware, and spread to shared drives and other systems. The fallout can include downtime, breach costs, regulatory trouble, and lost customer trust.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, block or quarantine Office files from unknown senders, keep Protected View on for files from the internet, use attack surface reduction rules to stop Office apps from launching child processes, and remind users not to open unexpected attachments.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. It needs no credentials, only a user who opens a file, and Excel is installed on almost every business desktop. Spreadsheet lures are one of the most common phishing tricks, so the gap between a fix and real attacks can be short. Deploy the Office update across all affected editions, and Office Online Server where used, as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119382 – Windows TPM Elevation of Privilege Vulnerability

“The chip built to protect your secrets could become the attacker's ladder to full control.”

CVE-2026-119382 is a heap-based buffer overflow in the Windows Trusted Platform Module (TPM) components. An attacker who already has a low-privileged account on the system can trigger the overflow locally and raise their privileges. The flaw affects all supported Windows client and server versions in the update.

CVSS Score: 7.8

SEVERITY: Critical

THREAT: A local attacker with a standard user account could exploit this bug to gain higher privileges and take full control of the machine.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Windows TPM handling. A low-privileged local user can send crafted input that causes Windows to write past a heap buffer. This memory corruption can be used to run code in a more privileged context. The attack is local, low complexity, needs low privileges, and requires no user interaction. A successful attack has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. The attacker must first be able to run code on the system as a regular user, then trigger the bug locally.

BUSINESS IMPACT: Privilege escalation bugs turn a small breach into a big one. An attacker who lands on one workstation through phishing or malware can use this flaw to gain full control, disable defenses, and harvest credentials. Because the TPM is tied to security features like BitLocker and Windows Hello, tampering here hits trust at its core.

WORKAROUND: No official workarounds are listed. Limit local logon rights, enforce least privilege, and use application control to block untrusted code until the patch is in place.

URGENCY: Microsoft rates this Critical, and the attack is simple once an attacker is on the box. Attackers routinely chain bugs like this with phishing to go from user to full control. Every supported Windows version is affected, so patch broadly and quickly.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119969 – Graphic Fonts Remote Code Execution Vulnerability

“One poisoned font is all it takes. Open the wrong file, and an attacker could be running code on your machine.”

CVE-2026-119969 is a heap-based buffer overflow in the Windows Graphic Fonts component. An attacker who gets a user to open or view specially crafted content can overflow memory while the font is processed and run code on the system. It affects every supported Windows client and server release in the update.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated remote attacker who tricks a user into opening malicious content could run code with that user's rights and take control of the system.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in how Windows handles graphic fonts. When a crafted font is parsed, Windows writes past the end of a heap buffer, corrupting nearby memory. An attacker can shape that corruption to redirect execution and run their own code. The attack works over a network, needs low complexity and no privileges, but does require the user to take an action such as opening a file or visiting content. A successful attack fully compromises confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. An attacker delivers a weaponized font inside a document, email, or web content and waits for a user to open or preview it.

BUSINESS IMPACT: Fonts are everywhere: documents, emails, web pages, and presentations. That makes this an easy bug to hide inside everyday business files. One click by one employee could give an attacker a foothold to steal data, plant ransomware, or move deeper into the network.

WORKAROUND: No official workarounds are listed. Until you patch, block untrusted documents and attachments at the email gateway, use Protected View for Office files, and limit user privileges so a successful attack does less damage.

URGENCY: This bug is rated Critical, reachable over the network, and needs no credentials, just one user action. Font handling is built into every Windows system in the list, from laptops to servers, so the attack surface is huge. Patch quickly before attackers turn this into a phishing payload.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119967 – Windows Message Queuing Queue Manager Remote Code Execution Vulnerability

An open queue is an open door. If MSMQ accepts anonymous web requests, a single packet could be all an attacker needs.

CVE-2026-119967 is a use-after-free flaw in the Windows Message Queuing Queue Manager. An unauthenticated attacker could send a specially crafted packet to an affected service and run code on the target system, with no user interaction. The attack only works when Message Queuing HTTP support is enabled and set up to accept anonymous requests, and the attacker cannot turn that setting on through this bug.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated attacker who can reach an MSMQ server with anonymous HTTP support enabled could run code on it. That would give them a foothold on a server that often handles business application traffic.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The bug is a use-after-free (CWE-416) in the Message Queuing Queue Manager. A crafted packet can make the service use memory after it has been freed, which an attacker can turn into code execution. The CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. It needs no credentials or user action, but the complexity is high because the target must have Message Queuing HTTP support enabled and configured to process anonymous requests.

EXPLOITABILITY: Affected: Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. Only systems with Message Queuing HTTP support enabled and accepting anonymous requests are exploitable; the attacker sends a crafted packet over the network. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025).

BUSINESS IMPACT: Servers that expose MSMQ over HTTP are often tied to line-of-business apps and integrations with partners. A compromise could lead to data theft, tampered transactions, or ransomware spreading from a trusted application server. Because anonymous access is part of the attack path, there is no login barrier to slow an attacker down.

WORKAROUND: Microsoft lists no mitigations or workarounds. If you cannot patch, disable Message Queuing HTTP support where it is not needed, turn off anonymous access to it, and block MSMQ traffic from untrusted networks.

URGENCY: This is a Critical, unauthenticated remote code execution bug in a service with a long track record of serious flaws. The required configuration narrows the target list, but any system that matches is fully exposed. Find MSMQ servers with HTTP support enabled and patch them right away.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119963 – Windows Message Queuing Remote Code Execution Vulnerability

“One crafted packet, no password, no click: that is all it takes to turn a Message Queuing server into an attacker's launch pad.”

CVE-2026-119963 is a remote code execution flaw in Windows Message Queuing (MSMQ). A double free bug in the service lets an attacker who has no account on the system send a specially crafted packet and run code on the target. It affects a wide range of supported Windows client and server versions, and the attacker needs no credentials and no help from a user.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated attacker anywhere on the network could send crafted packets to a Windows system running Message Queuing and run their own code on it. No login and no user click are needed.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a double free (CWE-415) in the Windows Message Queuing service. When the service processes a malicious packet, it can release the same block of memory twice. That corrupts the memory manager's internal state, and a skilled attacker can shape that corruption to take control of the program's flow and execute code. The attack runs over the network, needs no privileges and no user interaction, and a successful exploit can fully compromise confidentiality, integrity and availability on the target. Attack complexity is high because specific protocol settings or configurations must be in place first.

EXPLOITABILITY: Affected versions include Windows 10 (versions 1607, 1809, 21H2 and 22H2), Windows 11 (versions 23H2, 24H2, 25H2, 26H1 and 26H2), and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker sends a specially crafted packet to the Message Queuing service over the network. The attack only works when specific conditions, such as particular protocol settings or configurations, are in place, which makes it harder to pull off at scale.

BUSINESS IMPACT: Message Queuing often runs on servers that move orders, transactions and messages between business applications. Code execution on such a server hands an attacker a trusted foothold inside the network, where they can steal data, tamper with business messages, deploy ransomware or move to other systems. Because no login is required, a single exposed MSMQ endpoint could be the starting point of a full breach.

WORKAROUND: No official mitigations or workarounds are listed. If you cannot patch right away, disable the Message Queuing service on systems that do not need it, and block inbound traffic to the Message Queuing port (TCP 1801) at the host and network firewall so only trusted systems can reach it.

URGENCY: This flaw is rated Critical, is reachable over the network, and needs neither credentials nor user action. Even though conditions must line up for an attack to work, the payoff is full code execution on Windows servers and workstations that are found in almost every organization. Message Queuing has a history of serious network-reachable bugs, so attackers are likely to study this patch. Deploy the update quickly, starting with any system where Message Queuing is enabled or reachable from untrusted networks.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119964 – Windows Message Queuing Remote Code Execution Vulnerability

“When a message service can be tricked into freeing the same memory twice, an attacker gets a free pass to run code on your servers.”

CVE-2026-119964 is another remote code execution flaw in Windows Message Queuing (MSMQ). A double free bug lets an unauthenticated attacker send a specially crafted packet over the network and execute code on the target system. It affects nearly every supported version of Windows client and server, and it needs no credentials and no user interaction.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated attacker anywhere on the network could send crafted packets to a Windows system running Message Queuing and run their own code on it. No login and no user click are needed.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The root cause is a double free (CWE-415) in the Message Queuing service. While handling a malicious packet, the service frees the same memory more than once. This leaves memory in a corrupted state that an attacker can abuse to redirect execution and run code. The attack runs over the network, needs no privileges and no user interaction, and success means full impact to confidentiality, integrity and availability. Attack complexity is high, because particular protocol settings or configurations must be in place before the attack can succeed.

EXPLOITABILITY: Affected versions include Windows 10 (versions 1607, 1809, 21H2 and 22H2), Windows 11 (versions 23H2, 24H2, 25H2, 26H1 and 26H2), and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker sends a specially crafted packet to the Message Queuing service over the network. The attack only works when specific conditions, such as particular protocol settings or configurations, are in place, which makes it harder to pull off at scale.

BUSINESS IMPACT: Many line-of-business applications depend on Message Queuing to pass orders, payments and system events between servers. If an attacker gains code execution on one of these servers, they can read or alter sensitive business messages, disrupt critical workflows, plant ransomware, and use the server as a stepping stone into the rest of the network. The lack of any login requirement makes exposed MSMQ systems an easy first target.

WORKAROUND: No official mitigations or workarounds are listed. If you cannot patch right away, disable the Message Queuing service on systems that do not need it, and block inbound traffic to the Message Queuing port (TCP 1801) at the host and network firewall so only trusted systems can reach it.

URGENCY: This vulnerability is rated Critical, can be reached over the network, and requires no account or user action. It ships alongside a sister flaw in the same service, which doubles the attention attackers will give to Message Queuing this month. The high attack complexity slows attackers down but does not stop them. Roll out the update promptly, and treat any server with Message Queuing enabled as a top priority.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119966 – Windows Graphics Kernel Elevation of Privilege Vulnerability

“An admin account is powerful; a flaw that pushes past it into the kernel is far worse.”

CVE-2026-119966 is an integer overflow in the Windows Graphics Kernel. An attacker who already has high privileges on a system could use it locally to elevate further and break out of the current security scope. Microsoft rates it Critical.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: A local attacker who already holds high privileges could exploit this flaw to gain even greater control, crossing a security boundary into a more privileged context.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is an integer overflow or wraparound (CWE-190) in the Windows Graphics Kernel. When a calculation exceeds the size of its number type, it can wrap to a small value and lead to memory being sized or accessed incorrectly. An attacker can use this to corrupt kernel memory and elevate privileges. The CVSS vector (AV:L/AC:H/PR:H/UI:N/S:C) shows a local attack that needs high privileges and is complex to pull off, but the scope is changed, so the impact reaches beyond the vulnerable component. Confidentiality, integrity and availability impacts are all high.

EXPLOITABILITY: Affected versions are Windows 11 versions 23H2, 24H2, 25H2 and 26H2 (x64 and ARM64), and Windows Server 2025, including Server Core. An attacker needs local, high-privileged access to trigger the overflow.

BUSINESS IMPACT: Attackers who already have admin-level access use bugs like this to escape sandboxes or security boundaries and hide deeper in the system. That makes it harder to detect and remove them. The result can be persistent compromise, disabled security tools and wider damage across the network.

WORKAROUND: Microsoft lists no mitigations or workarounds. Reduce the number of accounts with high privileges and closely monitor privileged activity until the update is installed.

URGENCY: Microsoft rates this Critical because a successful attack crosses a security boundary. The need for high privileges lowers the immediate risk, but this kind of bug is valuable in attack chains after an initial compromise. Fixes are in KB5131087 (Windows 11 23H2), KB5132061 and KB5132043 (Windows 11 24H2/25H2/26H2), and KB5131080 and KB5131077 (Server 2025), and a restart is required.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119962 – Windows CredSSP Remote Code Execution Vulnerability

The protocol built to protect your credentials could become the doorway attackers use to take over the machine.

CVE-2026-119962 is a Critical remote code execution vulnerability in the Windows Credential Security Support Provider (CredSSP) protocol. A double free memory bug lets an unauthenticated attacker send network traffic that could lead to code execution on the target. No user interaction is needed, although the attack is complex to pull off. The flaw affects a wide range of Windows client and server versions, from Windows 10 version 1607 and Windows Server 2016 up to Windows 11 version 26H2 and Windows Server 2025.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: A remote, unauthenticated attacker who can reach a system over the network could run code on it without any user help, potentially taking full control.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is a double free (CWE-415) in the Windows CredSSP protocol, the component Windows uses to securely delegate user credentials during authentication, for example with Remote Desktop and remote management. A double free happens when the same block of memory is released twice, which corrupts memory management and can let an attacker control what code runs next. The CVSS v3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The attack comes over the network and needs no privileges or user interaction, but high attack complexity means the attacker must meet conditions outside their direct control to succeed. If they do, the impact on confidentiality, integrity, and availability is high.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. An attacker would need network access to a system using CredSSP and would send crafted traffic to trigger the double free.

BUSINESS IMPACT: CredSSP sits in the authentication path for remote access, which many organizations depend on to manage servers and support users. A successful attack could hand an outsider control of a server or workstation without a single password or click. That can mean data theft, ransomware deployment, and lateral movement across the network. Because servers and admin systems are often where CredSSP is used most, the blast radius of a compromise could be large.

WORKAROUND: No official mitigation or workaround is listed, so the update is the fix. Until it is installed, limit network access to remote access services that rely on CredSSP, such as Remote Desktop and WinRM, to trusted management networks or VPN only, and make sure they are not exposed to the internet.

URGENCY: This is a Critical, no-click, network-reachable flaw in a core Windows authentication component, and it touches almost every supported Windows client and server. High attack complexity slows attackers down, but it does not stop them. Exposed servers and remote access gateways should be patched first, followed by the rest of the fleet in this cycle. A restart is required, so plan maintenance windows now.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119960 – Windows Hyper-V Elevation of Privilege Vulnerability

“The wall between virtual machines is only as strong as its weakest byte. Leftover data in Hyper-V can give a privileged attacker a path through it.”

This vulnerability affects Windows Hyper-V, the virtualization layer that runs virtual machines on Windows 11 and Windows Server 2025. Hyper-V uses a resource before it is properly set up, and an attacker who already has high privileges on the system can abuse that to raise their privileges further. Because the scope is changed, the impact can reach past the component where the bug lives. Microsoft rates it Critical.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: A local attacker who already has high privileges could use this flaw to gain even more control, potentially crossing the security boundary that Hyper-V is meant to enforce.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-908, Use of Uninitialized Resource. Hyper-V reads or uses memory or another resource that has not been initialized, so its contents are whatever was left behind. An attacker who can influence that leftover state may be able to steer how Hyper-V behaves. The CVSS vector is AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H: local access, high complexity, high privileges required, no user interaction, and a changed scope with high impact to confidentiality, integrity, and availability. The changed scope is the key point: the attack can affect resources beyond the attacker's starting security context.

EXPLOITABILITY: Affected: Windows 11 versions 24H2, 25H2, 26H1, and 26H2 (x64 and ARM64), and Windows Server 2025 including Server Core. Fixes ship in KB5132061, KB5132043, KB5132059, KB5131080, and KB5131077, depending on the version. Exploitation needs local access, high privileges, and specific conditions, so it is not easy to pull off.

BUSINESS IMPACT: Hyper-V hosts often run many workloads at once, so a break in the virtualization boundary can affect far more than one machine. An attacker who gets deeper control of a host could tamper with or read data from other workloads, disrupt services, or hide their presence. For organizations that rely on Windows Server 2025 for virtualization, this can mean wide outages and data exposure from a single compromised foothold.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, limit who holds administrative rights on Hyper-V hosts and guests, and monitor privileged activity closely.

URGENCY: This flaw is rated Critical and targets the virtualization layer that holds many workloads together. Although it needs high privileges and is complex to exploit, attackers who already have a foothold look for exactly this kind of step-up. Patch Hyper-V hosts in the next maintenance window, and note that a restart is required for most affected versions.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119961 – Windows Internet Information Services Remote Code Execution Vulnerability

“Your web server could be one lucky race away from running someone else's code, with no login required.”

CVE-2026-119961 is a race condition that leads to a use-after-free in Windows Internet Information Services (IIS). An unauthenticated attacker can send a specially crafted packet to an affected service and run code on the target system. No user interaction is needed, but the attacker must win a race condition.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated remote attacker could run code on an IIS server and take control of it.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw combines improper synchronization of a shared resource (CWE-362) with a use-after-free (CWE-416) in IIS. When two operations hit the same resource at the wrong time, IIS can use memory that was already freed. An attacker who wins this race with crafted packets can take over execution. The attack is over the network, with high complexity, no privileges, and no user interaction. A successful attack has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. Systems with IIS installed are exposed. An attacker sends crafted packets to the service over the network and tries to win the race.

BUSINESS IMPACT: IIS often hosts public websites, APIs, and internal portals, many of them facing the internet. A compromised web server can leak customer data, serve malware to visitors, and give attackers a launch point into the internal network. Downtime and data exposure hit both revenue and reputation.

WORKAROUND: No official workarounds are listed. Remove IIS where it is not needed, limit internet exposure of IIS servers, and place them behind a web application firewall or reverse proxy.

URGENCY: This is a Critical, unauthenticated, no-click bug in a web server that is often exposed to the internet. Attackers can try the race again and again with automated tools. Patch internet-facing IIS servers first.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119958 – Windows LDAP – Lightweight Directory Access Protocol Remote Code Execution Vulnerability

Your directory is the map to your whole network. This LDAP flaw could hand that map, and the keys, to an attacker who never logged in.

CVE-2026-119958 is an out-of-bounds write in Windows LDAP, the Lightweight Directory Access Protocol. An unauthenticated attacker could send a specially crafted set of LDAP calls and run arbitrary code within the context of the LDAP service. With a CVSS score of 9.8, low attack complexity, and no user interaction, this is one of the most serious bugs in the release.

CVSS Score: 9.8

SEVERITY: Critical

THREAT: An unauthenticated attacker on the network could run code inside the LDAP service. On domain controllers, that could put the entire Active Directory environment at risk.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is an out-of-bounds write (CWE-787) in the Windows LDAP implementation. A specially crafted sequence of LDAP calls can cause the service to write data outside the memory it owns, which an attacker can use to run code in the context of the LDAP service. The CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. That means it is reachable over the network, easy to trigger, needs no credentials or user action, and has a full impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected: Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An unauthenticated attacker sends crafted LDAP calls to a system running the LDAP service. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025).

BUSINESS IMPACT: LDAP is the backbone of directory services and identity, and it runs on every domain controller. A compromised domain controller can mean stolen credentials, rogue admin accounts, and domain-wide ransomware. Recovery from a directory compromise is slow and expensive, and it often means rebuilding trust across the whole environment.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, make sure LDAP ports (389, 636, 3268, 3269) are not reachable from the internet or untrusted segments, and watch domain controllers for unusual LDAP traffic or service crashes.

URGENCY: A 9.8 score, no authentication, low complexity, and a target as central as LDAP make this a top-priority patch. Attackers watch for bugs like this because they can lead straight to domain compromise. Patch domain controllers and other LDAP-facing servers first.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119957 – Windows Remote Desktop Services Elevation of Privilege Vulnerability

“One lost race is all it takes for a low-level foothold to become control of the host.”

CVE-2026-119957 is a double free bug in Windows Remote Desktop Services. An attacker who already has a low-privileged account on an affected server can trigger the flaw locally and, by winning a race condition, raise their privileges. Microsoft rates it Critical because the scope is changed, which means the damage can reach beyond the component that has the bug.

CVSS Score: 7.8

SEVERITY: Critical

THREAT: A logged-in attacker with low privileges, including one working from inside a guest virtual machine, could exploit this flaw to gain the privileges of the affected service on the host.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a double free (CWE-415) in Windows Remote Desktop Services, where the same block of memory can be released twice. Freeing memory twice can corrupt the heap and let an attacker steer what ends up in that memory, which can lead to code running with higher privileges. Microsoft says exploitation requires the attacker to win a race condition, so the attack is not simple or fully reliable. The CVSS vector (AV:L/AC:H/PR:L/UI:N/S:C) shows a local attack needing low privileges and no user action, with a changed scope and high impact to confidentiality, integrity and availability. Microsoft notes that a successful attacker operating inside a guest virtual machine could gain the privileges of the affected virtualization service on the host.

EXPLOITABILITY: Affected versions are Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker needs local, low-privileged access and must win a race condition to trigger the double free.

BUSINESS IMPACT: Remote Desktop servers and virtualization hosts often sit at the heart of a business, serving many users at once. If a low-privileged user or a compromised guest can break out to host-level privileges, the attacker may reach every session, workload and credential on that machine. That can turn one small compromise into data theft, ransomware staging or a full server takeover.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the update is installed, limit who can sign in to affected servers, keep untrusted workloads off shared hosts, and watch for unusual privilege changes.

URGENCY: Microsoft rates this Critical, and the changed scope means a successful attack can cross a security boundary. The race condition makes exploitation harder, but attackers routinely chain local privilege bugs with initial access to finish the job. Because it affects every supported Windows Server release from 2016 to 2025, patch servers that host Remote Desktop or shared workloads first.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119952 – Windows Schannel Remote Code Execution Vulnerability

“The layer that keeps your connections private could be the very thing that lets an attacker inside.”

CVE-2026-119952 is a remote code execution flaw in Windows Schannel, the Windows component that handles TLS and SSL for secure connections. It comes from an observable timing discrepancy and lets an unauthenticated attacker run code by sending a crafted packet, with no user action needed. Microsoft rates it Critical and considers exploitation more likely.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated remote attacker could send crafted packets to a service that uses Schannel and run code on the target system, without any user interaction.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known. Attackers are considered more likely to target it.

TECHNICAL SUMMARY: The flaw is an observable timing discrepancy (CWE-208) in Windows Schannel, the security provider that secures TLS and SSL traffic for many Windows services. Timing differences in how Schannel handles certain input can be abused so that a specially crafted packet leads to code execution on the target. Microsoft says no authentication or user interaction is needed, but the attack only works when specific conditions, such as particular protocol settings or configurations, are in place. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U) shows a network attack with high complexity and high impact to confidentiality, integrity and availability.

EXPLOITABILITY: Affected versions are Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2 (x64, ARM64 and 32-bit where applicable); and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker sends crafted packets to a Schannel-backed service and needs specific protocol settings or configurations to be in place.

BUSINESS IMPACT: Schannel protects web servers, remote access, email and many internal services that rely on TLS. A remote code execution bug in this layer puts internet-facing systems directly in the line of fire. Exploitation could lead to server takeover, theft of sensitive data and certificates, and a serious hit to customer trust.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the update is applied, limit exposure of TLS services to trusted networks where possible and monitor internet-facing servers closely.

URGENCY: This is a Critical, no-click, no-credential bug in a component almost every Windows server exposes. Microsoft considers exploitation more likely, and every supported Windows release is affected. Patch internet-facing servers first. Fixes ship in the November cumulative updates, including KB5131291 (Windows 10 1607 and Server 2016), KB5131085 (Windows 10 1809 and Server 2019), KB5131096 (Windows 10 21H2/22H2), KB5131087 (Windows 11 23H2), KB5132061 and KB5132043 (Windows 11 24H2/25H2/26H2), KB5132059 (Windows 11 26H1), KB5131090 (Server 2022), and KB5131080 and KB5131077 (Server 2025). A restart is required.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119951 – Windows Deployment Services Remote Code Execution Vulnerability

“No password, no click, just one crafted packet. The server that builds your machines could be the one an attacker takes over.”

This is a use-after-free flaw in Windows Deployment Services (WDS), the Windows Server role used to install operating systems over the network. An attacker with no credentials can send a specially crafted packet to the service and run code on the server. No user interaction is needed. The attack needs specific conditions to be in place, which raises the bar, but Microsoft still rates it Critical.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated attacker on the network could take over a Windows Deployment Services server, gaining control of a system that shapes how new machines are built.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-416, Use After Free. WDS frees memory while handling network traffic and later uses it again, letting a crafted packet corrupt memory and redirect execution. The CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H: network, high complexity, no privileges, no user interaction, with high impact. Microsoft explains that the high complexity means particular protocol settings or configurations must be in place for an attack to succeed, which reduces the chance of widespread, opportunistic attacks.

EXPLOITABILITY: Affected: Windows Server 2016, 2019, 2022, and 2025, including Server Core installations, where the WDS role is in use. Fixes are KB5131291 (2016), KB5131085 (2019), KB5131090 (2022), and KB5131080 or KB5131077 (2025). A restart is required. Exploitation means sending a crafted packet to the WDS service when the needed conditions exist.

BUSINESS IMPACT: Deployment servers are trusted infrastructure. If an attacker controls one, they could tamper with operating system images and push backdoored builds to every machine installed from it. That turns one compromised server into a supply-chain problem inside your own network. Recovery would mean rebuilding trust in every system that was deployed after the compromise.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, restrict network access to WDS servers to the deployment segments that need them, and disable or remove the WDS role where it is not used.

URGENCY: This flaw is Critical, needs no credentials, and needs no user action. The high complexity lowers the odds of mass attacks, but a deployment server is a high-value target worth extra effort for a determined attacker. Patch WDS servers promptly across all supported Windows Server versions and plan for the restart.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119947 – Windows Hyper-V Elevation of Privilege Vulnerability

When the virtual walls fail, every workload on the host is in play. This Hyper-V bug turns a guest VM into a launch pad against the host.

CVE-2026-119947 is another use-after-free flaw in Windows Hyper-V. An attacker who controls a guest virtual machine could exploit it to execute code on the host in the context of the virtual machine worker process. It is rated Critical because it breaks the isolation between guests and the host, even though the attacker must win a race condition to succeed.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: A privileged attacker inside a guest VM could escape to the Hyper-V host. That gives them a path to other VMs running on the same machine.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a use-after-free (CWE-416) in Hyper-V. Memory is freed and then used again, and an attacker in the guest can try to control that memory to gain code execution on the host in the security context of the virtual machine worker process. The CVSS vector is AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H. The attacker needs high privileges in the guest, and the attack complexity is high because it depends on winning a race condition. The changed scope means the damage reaches beyond the guest into the host.

EXPLOITABILITY: Affected: 64-bit and ARM64 editions of Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker with high privileges in a guest VM must win a race condition to run code on the host. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025).

BUSINESS IMPACT: Virtualization hosts concentrate risk, because one host can run many critical servers. A guest escape can expose databases, domain controllers, and file servers that share the host. The result could be data theft, sabotage of multiple systems at once, and costly downtime across many services.

WORKAROUND: Microsoft lists no mitigations or workarounds. Reduce risk by limiting admin access in guest VMs, keeping untrusted workloads on separate hosts, and monitoring hosts for unusual worker process behavior.

URGENCY: This is a Critical isolation break in Hyper-V, and it ships alongside a second Hyper-V guest escape this month. Hypervisors are high-value targets, and one successful attack affects every VM on the host. Patch virtualization hosts early in your rollout.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-124185 – Microsoft Office Word Remote Code Execution Vulnerability

“One opened document is all it takes to turn a routine workday into a full system compromise.”

CVE-2026-124185 is a remote code execution flaw in Microsoft Office Word caused by the use of an uninitialized resource. An attacker could send a malicious Office file and, if the user opens it, run code on their computer. Microsoft rates it Critical.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An unauthenticated attacker who convinces a user to open a malicious Office file could run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a use of uninitialized resource (CWE-908) in Microsoft Office Word. When Word processes a specially crafted file, it can use memory or another resource before it has been properly set up, and an attacker can influence what that resource contains to gain code execution. Microsoft says the attacker must send the file and convince the user to open it, and that success depends on factors such as the environment, system configuration and other security measures. The CVSS vector (AV:N/AC:H/PR:N/UI:R/S:U) shows a network attack with high complexity, no privileges needed and user interaction required, with high impact to confidentiality, integrity and availability.

EXPLOITABILITY: Affected versions are Microsoft 365 Apps for Enterprise and Microsoft Office LTSC 2021 and LTSC 2024, in both 32-bit and 64-bit editions. An attacker must deliver a malicious Office file and get the user to open it.

BUSINESS IMPACT: Word documents are part of everyday business, and phishing with booby-trapped attachments remains one of the most common ways attackers get in. One opened file on one workstation can give an attacker a foothold to steal data, harvest credentials and spread to other systems.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the update is applied, be cautious with Office files from unknown senders, keep Protected View enabled, and use email filtering to block suspicious attachments.

URGENCY: Microsoft rates this Critical, and Office is installed on nearly every corporate desktop. Phishing gives attackers an easy delivery path, even if the exploit itself is complex. Make sure Microsoft 365 Apps and Office LTSC installations pick up the latest build through their normal update channel.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-124170 – Microsoft Office Excel Remote Code Execution Vulnerability

“One poisoned spreadsheet is all it takes: open the wrong Excel file, and an attacker could be running code on your machine.”

CVE-2026-124170 is a remote code execution flaw in Microsoft Office Excel. A heap-based buffer overflow lets an attacker run code on a victim's computer if they can get the user to open a malicious Office file. It affects Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024, and Office Online Server.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An attacker who sends a booby-trapped Excel file could run code on the victim's computer with that user's rights. This could give them access to the user's data and a foothold in the network.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Excel. When Excel processes a specially crafted file, it writes more data into a heap memory buffer than the buffer can hold. The extra data overwrites nearby memory, which an attacker can use to take control of the program and run code. The attacker needs no privileges, but the victim must open the malicious file. Attack complexity is high: success needs a deep understanding of the system and depends on the environment, configuration and other security measures in place. If it works, the impact on confidentiality, integrity and availability is high.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 and 2024 (32-bit and 64-bit editions), and Office Online Server. An attacker must send a user a malicious Office file and convince them to open it, for example through a phishing email or a shared file.

BUSINESS IMPACT: Excel files move constantly between employees, customers and partners, which makes them a natural phishing lure. A single successful attack could expose financial data, customer records and credentials on the user's machine, and give the attacker a starting point for ransomware or deeper network intrusion. Office Online Server is also affected, which widens the exposure to server-side file handling.

WORKAROUND: No official mitigations or workarounds are listed. Until the update is installed, warn users about unexpected Excel attachments, keep Protected View enabled for files from the internet, and use email filtering and attachment sandboxing to catch malicious files.

URGENCY: This flaw is rated Critical and affects Excel, one of the most widely used business applications in the world. Malicious documents are a favorite phishing tool, and a convincing email is often all an attacker needs to get a file opened. Although the attack is complex, the reach of Office makes it an attractive target. Update Microsoft 365 Apps, Office LTSC and Office Online Server quickly.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-120005 – Microsoft PowerPoint Remote Code Execution Vulnerability

A slide deck should share ideas, not hand over your computer. One rigged PowerPoint file can do just that.

CVE-2026-120005 is a heap-based buffer overflow in Microsoft PowerPoint that can let an attacker run code on a user's computer. The attacker has to get the user to open a specially crafted presentation file. Once opened, the attacker's code runs with the user's permissions, and no prior access to the system is needed.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can deliver a file to a user, through email, a download, or a shared link, can attempt this attack. If the user opens the file, the attacker can take control of the user's session and data.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in PowerPoint. When PowerPoint processes a crafted presentation, it writes more data into a heap buffer than the buffer can hold. This overwrites nearby memory, which an attacker can use to change program behavior and run their own code. The attack is network-based with low complexity and needs no privileges, but it does require the user to open the file. Success brings high impact to confidentiality, integrity, and availability.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). The attacker crafts a malicious PowerPoint file and convinces the user to open it.

BUSINESS IMPACT: Presentations move constantly between staff, partners, and customers, so a malicious deck blends right in. If an employee opens one, the attacker gets a foothold to steal sensitive files, harvest credentials, and launch ransomware or wider attacks. Sales, marketing, and leadership teams, who open outside presentations every day, face the highest exposure.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until patched, block or quarantine Office files from untrusted sources, keep Protected View turned on, and remind users not to open unexpected presentations.

URGENCY: PowerPoint is installed on most business desktops, and opening a file is about the easiest thing an attacker can ask a user to do. The bug is rated Critical, there is no workaround, and file-based Office attacks are a common first step in breaches. Deploy the update quickly to close this door.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-120789 – Microsoft Office Excel Remote Code Execution Vulnerability

Every opened spreadsheet is a chance for attackers: this Excel flaw turns a routine file into a remote takeover.

CVE-2026-120789 is a Critical remote code execution vulnerability in Microsoft Office Excel. A heap-based buffer overflow can be triggered when a user opens a specially crafted workbook and interacts with affected features, allowing an attacker to run code as the signed-in user. Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024, and Office Online Server are affected and should be updated.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated attacker who tricks a user into opening a malicious workbook could run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Microsoft Office Excel. When Excel processes a specially crafted workbook and the user interacts with the affected workbook features, data can be written past the end of a memory buffer on the heap. An attacker who controls that overflow can corrupt memory and steer Excel into running their own code in the context of the signed-in user. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, which means the attack is delivered over the network, is low in complexity, needs no privileges, but does need the user to take action. A successful attack gives full impact on confidentiality, integrity, and availability for that user's session.

EXPLOITABILITY: Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit editions), and Office Online Server (fixed by update 5002946) are affected. An attacker has to convince a user to open a specially crafted workbook in Excel and interact with the affected features, typically through a phishing email, a shared link, or a file share.

BUSINESS IMPACT: Excel sits on nearly every business desktop, and spreadsheets are among the most trusted files people open every day. A single opened invoice, report, or budget file could give an attacker a foothold on a workstation, with access to the user's email, documents, and saved credentials. From there, attackers can steal data, install ransomware, or move deeper into the network. Finance, HR, and executive teams, who handle spreadsheets constantly, are prime targets.

WORKAROUND: No official mitigation or workaround is listed, so patching is the real fix. Until then, tell users not to open Excel files from unknown or unexpected senders, keep Protected View on for files from the internet and email, and filter or block risky spreadsheet attachments at the mail gateway.

URGENCY: This is rated Critical with a CVSS score of 8.8, needs no privileges, and targets one of the most widely used business applications in the world. The attack path is simple and familiar: send a file, get it opened. Even though no exploitation has been seen yet, Excel file bugs are a favorite phishing tool, so update Microsoft 365 Apps, Office LTSC, and Office Online Server in this patch cycle.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-120788 – Microsoft Office Excel Remote Code Execution Vulnerability

One spreadsheet is all it takes: open the wrong workbook, and an attacker could be running code on your machine.

CVE-2026-120788 is a Critical remote code execution vulnerability in Microsoft Office Excel. It comes from a heap-based buffer overflow that can be triggered when a user opens a specially crafted workbook and interacts with certain workbook features. If that happens, an attacker could run code on the computer with the same rights as the signed-in user. Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024, and Office Online Server all need the update.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated attacker who tricks a user into opening a malicious workbook could run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Microsoft Office Excel. When Excel processes a specially crafted workbook and the user interacts with the affected workbook features, data can be written past the end of a memory buffer on the heap. An attacker who controls that overflow can corrupt memory and steer Excel into running their own code in the context of the signed-in user. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, which means the attack is delivered over the network, is low in complexity, needs no privileges, but does need the user to take action. A successful attack gives full impact on confidentiality, integrity, and availability for that user's session.

EXPLOITABILITY: Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit editions), and Office Online Server (fixed by update 5002946) are affected. An attacker has to convince a user to open a specially crafted workbook in Excel and interact with the affected features, typically through a phishing email, a shared link, or a file share.

BUSINESS IMPACT: Excel sits on nearly every business desktop, and spreadsheets are among the most trusted files people open every day. A single opened invoice, report, or budget file could give an attacker a foothold on a workstation, with access to the user's email, documents, and saved credentials. From there, attackers can steal data, install ransomware, or move deeper into the network. Finance, HR, and executive teams, who handle spreadsheets constantly, are prime targets.

WORKAROUND: No official mitigation or workaround is listed, so patching is the real fix. Until then, tell users not to open Excel files from unknown or unexpected senders, keep Protected View on for files from the internet and email, and filter or block risky spreadsheet attachments at the mail gateway.

URGENCY: This is rated Critical with a CVSS score of 8.8, needs no privileges, and targets one of the most widely used business applications in the world. The attack path is simple and familiar: send a file, get it opened. Even though no exploitation has been seen yet, Excel file bugs are a favorite phishing tool, so update Microsoft 365 Apps, Office LTSC, and Office Online Server in this patch cycle.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-120786 – Microsoft Office Excel Remote Code Execution Vulnerability

A trusted spreadsheet can turn into a weapon: crafted Excel files could let attackers take over a user's computer.

CVE-2026-120786 is a Critical remote code execution vulnerability in Microsoft Office Excel caused by a heap-based buffer overflow. An attacker who gets a user to open a specially crafted workbook and work with certain workbook features could run code with that user's permissions. The bug affects Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024, and Office Online Server.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated attacker who tricks a user into opening a malicious workbook could run code on that user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Microsoft Office Excel. When Excel processes a specially crafted workbook and the user interacts with the affected workbook features, data can be written past the end of a memory buffer on the heap. An attacker who controls that overflow can corrupt memory and steer Excel into running their own code in the context of the signed-in user. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, which means the attack is delivered over the network, is low in complexity, needs no privileges, but does need the user to take action. A successful attack gives full impact on confidentiality, integrity, and availability for that user's session.

EXPLOITABILITY: Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit editions), and Office Online Server (fixed by update 5002946) are affected. An attacker has to convince a user to open a specially crafted workbook in Excel and interact with the affected features, typically through a phishing email, a shared link, or a file share.

BUSINESS IMPACT: Excel sits on nearly every business desktop, and spreadsheets are among the most trusted files people open every day. A single opened invoice, report, or budget file could give an attacker a foothold on a workstation, with access to the user's email, documents, and saved credentials. From there, attackers can steal data, install ransomware, or move deeper into the network. Finance, HR, and executive teams, who handle spreadsheets constantly, are prime targets.

WORKAROUND: No official mitigation or workaround is listed, so patching is the real fix. Until then, tell users not to open Excel files from unknown or unexpected senders, keep Protected View on for files from the internet and email, and filter or block risky spreadsheet attachments at the mail gateway.

URGENCY: This is rated Critical with a CVSS score of 8.8, needs no privileges, and targets one of the most widely used business applications in the world. The attack path is simple and familiar: send a file, get it opened. Even though no exploitation has been seen yet, Excel file bugs are a favorite phishing tool, so update Microsoft 365 Apps, Office LTSC, and Office Online Server in this patch cycle.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-122194 – Microsoft Defender Remote Code Execution Vulnerability

“When the tool built to stop attacks can be tricked into running one, the guard becomes the gateway.”

CVE-2026-122194 is a remote code execution flaw in Microsoft Defender, caused by a NULL pointer dereference in the Microsoft Malware Protection Engine. An unauthenticated attacker could use it to run code over a network, but a user must take some action for the attack to work. Microsoft rates it Critical.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An unauthenticated remote attacker who gets a user to interact with malicious content could run code on the target machine, potentially with the high privileges the Defender engine uses.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The bug is a NULL pointer dereference (CWE-476) in the Microsoft Malware Protection Engine, the scanning core behind Microsoft Defender. When the engine processes certain input, it can use a pointer that does not point to valid memory. Microsoft says this can be used to execute code over a network. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U) shows a network attack with low complexity and no privileges needed, but it does need user interaction. Confidentiality, integrity and availability impacts are all high. Microsoft has not published further technical details.

EXPLOITABILITY: The affected product is the Microsoft Malware Protection Engine. An attacker would need a user to interact with attacker-supplied content so the engine processes it.

BUSINESS IMPACT: Defender runs on a huge number of Windows endpoints and servers, and it is trusted to inspect untrusted content. A flaw in the scanning engine turns that trust upside down: content meant to be blocked could become the way in. A successful attack could lead to malware installation, data theft and a weakened security posture across the fleet.

WORKAROUND: Microsoft lists no mitigations or workarounds. The fix is delivered through the normal engine update channel, so confirm that Defender engine updates are not blocked or delayed and that devices report the latest engine version.

URGENCY: Microsoft rates this Critical, it needs no privileges, and the vulnerable component is present on nearly every Windows system. Engine updates usually install automatically and need no restart, so the main task is to verify that every device, including offline and isolated ones, has received the updated engine.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-116928 – Microsoft Exchange Server Remote Code Execution Vulnerability

Nobody has to open anything. One email with a poisoned attachment could be enough to take over your mail server.

CVE-2026-116928 is an out-of-bounds write in Microsoft Exchange Server. An unauthenticated attacker could send an email with a specially crafted attachment to an affected Exchange server. The bug triggers when the server automatically processes the attachment for indexing, so the recipient never needs to open the email or the file. Successful exploitation could allow code execution with the permissions of the processing service, and the flaw carries a CVSS score of 9.8.

CVSS Score: 9.8

SEVERITY: Critical

THREAT: Anyone who can send email to your organization could run code on the Exchange server without credentials or user interaction. That puts mailboxes, credentials, and internal network access at risk.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is an out-of-bounds write (CWE-787) in how Exchange Server processes attachments for indexing. A crafted attachment causes the processing service to write outside its intended memory, which can lead to code execution with that service's permissions. The CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The attack comes over the network, is easy to trigger, needs no privileges, and needs no user action because indexing happens automatically when mail arrives.

EXPLOITABILITY: Microsoft's update data for this CVE lists these products and fixes: Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025). Exchange servers are exposed when they receive and index an email carrying a crafted attachment; no one needs to open it.

BUSINESS IMPACT: Exchange servers hold sensitive email, calendars, and contacts, and they are usually reachable from the internet by design. A compromise can lead to email theft, business email compromise, credential harvesting, and a jump into the internal network. The zero-click delivery through ordinary email makes this a fast and quiet way in.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, consider stricter attachment filtering at the email gateway, and watch Exchange servers for unusual activity from indexing or content processing services.

URGENCY: A 9.8 score, no authentication, and zero-click delivery by email make this one of the most urgent fixes this month. Exchange servers are constant targets, and attackers move quickly on mail server bugs. Patch Exchange servers as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-125137 – Windows Graphics Kernel Elevation of Privilege Vulnerability

One bad graphics call inside a virtual machine could hand an attacker the keys to the host itself. The wall between guest and host is only as strong as the code that guards it.

CVE-2026-125137 is a heap-based buffer overflow in the Windows Graphics Kernel. An attacker who already has a low-privilege foothold can abuse it to raise their privileges locally. What makes this one stand out is where those privileges land: Microsoft says a successful attacker could gain elevated rights on the host system, beyond the guest virtual machine boundary. That is why Microsoft rates it Critical, even though the base score sits at 7.8.

CVSS Score: 7.8

SEVERITY: Critical

THREAT: A logged-in attacker with low privileges inside a virtual machine could break out of that guest and gain high-level rights on the underlying host. From there, every workload on that host is in reach.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in the Windows Graphics Kernel. Code in the graphics stack writes more data into a heap buffer than the buffer can hold, corrupting nearby memory. An attacker who can trigger this overflow can steer that corruption to run code with higher privileges. The CVSS vector shows a changed scope (S:C), which means the impact reaches past the vulnerable component: in this case from a guest virtual machine to the host. Confidentiality, integrity, and availability are all rated High. Attack complexity is High because exploitation only works when the target virtual machine has multiple assigned graphics adapters with different configurations, a setup the attacker cannot control.

EXPLOITABILITY: Affected systems include Windows 10 versions 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2019, 2022, and 2025, including Server Core installations. The attacker needs local access with low privileges and no user interaction. Exploitation also depends on a virtual machine having multiple graphics adapters with differing configurations.

BUSINESS IMPACT: Virtualization exists to keep workloads apart. A guest-to-host escape breaks that promise. In shared or multi-tenant environments, one compromised virtual machine could become a launch point to the host and every other guest on it. That can mean stolen data across business units or customers, tampered systems, outages, and the cost and reputation damage that follow a breach of core infrastructure.

WORKAROUND: Microsoft lists no workaround or mitigation. Until the update is applied, review virtual machines that have multiple graphics adapters assigned, remove extra or mismatched adapters where they are not needed, and limit who can log on to those guests.

URGENCY: Microsoft rates this Critical because it can break the boundary between a guest and its host. It needs only a low-privilege account and no user interaction, and the affected Windows versions cover nearly every modern desktop and server. Hosts running virtual machines with GPU assignments should be patched first, followed by the rest of the fleet.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118207 – Microsoft Exchange Server Remote Code Execution Vulnerability

“Any mailbox can become a master key. One low-level account and one crafted request could put an attacker in charge of your mail server.”

This vulnerability affects Microsoft Exchange Server Subscription Edition. An attacker with a low-level authenticated account can send a specially crafted request to run code on the Exchange server. No user interaction is required. Microsoft rates it Critical and expects attackers are likely to go after it, which puts it high on the list for attackers who target email systems.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any attacker with a basic Exchange account, including one taken over through phishing, could run code on the mail server and gain control of a system that holds the organization's email.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known. Attacks are expected to be likely, so they could follow soon.

TECHNICAL SUMMARY: The weakness is listed as CWE-706, Use of Incorrectly-Resolved Name or Reference, and Microsoft's summary describes it as improper input validation. Exchange does not properly validate part of an incoming request and ends up resolving a name or reference to the wrong target, which an attacker can use to execute code on the server. The CVSS vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H: network, low complexity, low privileges, no user interaction, with high impact to confidentiality, integrity, and availability.

EXPLOITABILITY: Affected: Microsoft Exchange Server Subscription Edition RTM. The fix is KB5133453, and a restart is required. An attacker with any low-privileged authenticated access sends a crafted request to the server.

BUSINESS IMPACT: Exchange servers hold years of sensitive email and connect deeply into Active Directory. Attackers have repeatedly gone after Exchange because a single compromised server can expose confidential communications, enable business email fraud, and serve as a launch point for ransomware. A low bar for access means a single phished account could be enough.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, limit external access to Exchange, enforce multifactor authentication to protect accounts, and monitor Exchange logs for unusual requests and new processes.

URGENCY: This flaw is Critical, has a low-complexity network attack path, needs only a basic account, and is expected to be a likely attack target. Exchange is a long-standing favorite target. Install KB5133453 on every Exchange Server Subscription Edition server as soon as possible and plan the restart.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-125136 – Windows Network Connected Devices Auto-Setup Service Remote Code Execution Vulnerability

On a shared network, a fake device is all it takes. No password, no click, and your Windows machine could be running someone else's code.

CVE-2026-125136 is a heap-based buffer overflow in the Windows Network Connected Devices Auto-Setup Service, the feature that finds and sets up devices like printers on the local network. An attacker on the same network can advertise a specially crafted fake device, and if network device discovery is turned on, the affected system may run the attacker's code. No login and no user action are needed, which is why Microsoft rates it Critical.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Anyone who can reach the same local network segment, such as a rogue insider, a guest on office Wi-Fi, or an attacker on a hotel or coffee shop network, could take over a Windows device. They would gain the ability to run code on that device without any credentials.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in the Network Connected Devices Auto-Setup Service. When Windows discovers a device on the network, the service processes information the device advertises about itself. A specially crafted device announcement can cause the service to write past the end of a heap buffer, corrupting memory and letting the attacker run code. The CVSS vector shows an adjacent network attack (AV:A), low complexity, no privileges, and no user interaction, with High impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected systems include Windows 10 versions 1607, 1809, 21H2, and 22H2, and Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2. An unauthenticated attacker on the same local network advertises a malicious device to a system with network device discovery enabled. No user interaction is required.

BUSINESS IMPACT: Laptops move between offices, homes, airports, and hotels, and many of those networks are shared with strangers. A flaw that turns a fake printer announcement into code execution gives attackers a quiet way in. Once inside, they could steal data, plant ransomware, or move deeper into the corporate network the next time the device connects. The result can be data loss, downtime, and costly incident response.

WORKAROUND: Microsoft lists no workaround or mitigation. If the update cannot be applied right away, consider turning off network discovery on untrusted networks or disabling the Network Connected Devices Auto-Setup service where it is not needed, and keep devices off shared or public networks where possible.

URGENCY: Microsoft rates this Critical. The attack needs no credentials and no user action, only a spot on the same network, and the service runs across a wide range of Windows 10 and Windows 11 releases. Mobile users and devices on shared networks face the highest risk, so they should be patched first.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-119990 – Azure OpenAI Elevation of Privilege Vulnerability

When a critical function forgets to ask who you are, anyone on the network could walk in with elevated privileges.

CVE-2026-119990 is a Critical elevation of privilege vulnerability in Azure OpenAI. A critical function was missing authentication, which could let an unauthenticated attacker elevate privileges over the network. The attack needs no credentials and no user interaction, which is why it carries a CVSS score of 9.8. Microsoft lists customer action as required for this issue.

CVSS Score: 9.8

SEVERITY: Critical

THREAT: A remote attacker with no credentials could reach an unprotected critical function in Azure OpenAI and gain elevated privileges, opening the door to data and resources tied to the service.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The flaw is missing authentication for a critical function (CWE-306) in Azure OpenAI. A function that should have checked who was calling it did not, so an attacker could use it without proving their identity and end up with privileges they should never have. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H: network-based, low complexity, no privileges, and no user interaction. Successful exploitation has high impact on confidentiality, integrity, and availability. Microsoft does not give further technical detail on the affected function.

EXPLOITABILITY: The affected product is Azure OpenAI, and the fix is described in Microsoft's release notes. An attacker would send requests over the network to the unprotected function, with no credentials or user action needed. The specific affected versions or deployments are not listed in the data.

BUSINESS IMPACT: Organizations increasingly connect Azure OpenAI to internal data, applications, and workflows. Elevated access to that service could expose prompts, model outputs, connected data, and business logic, or let attackers misuse the service and run up costs. A breach here could leak sensitive information, damage trust in AI-driven processes, and create compliance problems.

WORKAROUND: No official mitigation or workaround is listed. Follow the actions in Microsoft's release notes for Azure OpenAI, and in the meantime restrict network access to Azure OpenAI resources with private endpoints or firewall rules, review access keys and role assignments, and watch activity logs for unusual requests.

URGENCY: A 9.8 CVSS score, Critical severity, and an attack that needs no credentials and no user interaction put this at the top of the list. Even though no exploitation is known, missing-authentication bugs are easy to find and abuse once details leak. Because Microsoft marks customer action as required, cloud and AI teams should confirm their Azure OpenAI resources are covered right away rather than assume the fix is automatic.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-111309 – Microsoft Office Outlook Remote Code Execution Vulnerability

Reading your email shouldn't put your computer at risk, but with this Outlook flaw one preview can do exactly that.

CVE-2026-111309 is a release of invalid pointer or reference flaw in Microsoft Office Outlook that lets an attacker run code on the victim's machine. The attack works when a user opens or previews a specially crafted email. In a typical scenario, the attacker sends the email and convinces the user to read it.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can send email to a user can try this attack. If the user opens or previews the message, the attacker can run code on the user's computer with the user's rights.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The bug is a release of invalid pointer or reference (CWE-763) in Outlook. While handling a crafted email, Outlook tries to free memory using a pointer that is not valid, which corrupts memory management. An attacker can use this to take control of program flow and run their own code. The Preview Pane is an attack vector, so simply viewing the message can trigger it. The attack is network-based with low complexity and no privileges needed, and it brings high impact to confidentiality, integrity, and availability.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). The attacker sends a crafted email and gets the user to open or preview it in Outlook.

BUSINESS IMPACT: Outlook sits at the center of daily work, and this bug turns routine email reading into a way in. A compromised mailbox can lead to data theft, business email compromise, fraudulent payments, and ransomware. Because a preview is enough, even careful users can be caught.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until patched, consider turning off the Reading Pane, reading mail in plain text, tightening email filtering, and removing local admin rights from users.

URGENCY: This is a Critical Outlook bug that can be triggered just by previewing an email, and there is no workaround. With Outlook used so widely, the attack surface is huge. Make this Office update a priority.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-111285 – Microsoft Office Word Remote Code Execution Vulnerability

A Word file doesn't have to be opened to cause trouble. Just a preview could be enough to hand over control.

CVE-2026-111285 is a heap-based buffer overflow in Microsoft Office Word that can let an attacker run code on a user's computer. The attacker needs the user to open a specially crafted file, and the Preview Pane is also an attack vector. Successful attacks run code with the permissions of the logged-in user.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can deliver a crafted document to a user can try this attack. Opening or previewing the file could let the attacker run code and take over the user's session.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Word. A crafted document causes Word to write data beyond the bounds of a heap buffer, corrupting memory that an attacker can use to run their own code. The Preview Pane is an attack vector, which lowers the amount of user action needed. The attack is network-based with low complexity and no privileges needed, and it brings high impact to confidentiality, integrity, and availability.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). The attacker sends a crafted Word file and gets the user to open or preview it.

BUSINESS IMPACT: When previewing a file is enough, the usual advice of "don't open strange attachments" is not enough protection. An attacker could steal files and credentials, use the hijacked account to spread further, or set up ransomware. Any team that handles outside documents is exposed.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until patched, consider turning off the Preview Pane in Outlook and File Explorer, keep Protected View on, and filter Office attachments from untrusted senders.

URGENCY: This is a Critical bug in one of the most common business apps, and the Preview Pane path means very little user action is needed. There is no workaround. Push the Office update quickly to shut this attack path down.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-110068 – Microsoft Office Outlook Remote Code Execution Vulnerability

One bad email in the inbox is all it takes. Open it, and an attacker can be running code on your machine.

CVE-2026-110068 is a use-after-free flaw in Microsoft Office Outlook that lets an attacker run code on a victim's computer. The attacker only needs to send a specially crafted email and get the user to open it in Outlook. No account on the target system is needed, and the code runs with the same rights as the user who opened the message.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can send an email to a user can try this attack. If the user opens the message, the attacker can run code with that user's permissions and take over their session, data, and mailbox.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The bug is a use-after-free (CWE-416) in Outlook. Outlook frees a piece of memory while handling a crafted email but keeps using a reference to it later. An attacker who shapes the email carefully can control what ends up in that freed memory and steer the program into running attacker-supplied code. The attack works over the network, needs low complexity and no privileges, but does require the user to open the message. A successful attack gives full impact on confidentiality, integrity, and availability within the user's context.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). Microsoft provides the fix through the Office release channels. An attacker sends a crafted email and convinces the user to open it in Outlook.

BUSINESS IMPACT: Email is the front door of every business, and this flaw turns a normal inbox action into a way in. A single opened message could give an attacker access to the user's files, mail, and saved credentials. From there, they can steal data, send convincing phishing mail from a trusted account, plant ransomware, or move deeper into the network. Executives, finance, and help desk staff, who open many outside emails, are especially attractive targets.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the update is applied, train users to be careful with unexpected emails, use email filtering to block suspicious messages, and run users without local admin rights to limit the damage.

URGENCY: This is a Critical remote code execution bug in one of the most widely used business apps in the world. The attack path is simple: send an email and wait for someone to open it. No exploitation is known yet, but email-based Office bugs are a favorite of attackers, and there is no workaround. Update Office as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-111289 – Microsoft Office Remote Code Execution Vulnerability

Just previewing the wrong file could be enough. This Office bug turns a quick glance at an attachment into a full takeover of the user's session.

CVE-2026-111289 is a remote code execution flaw in Microsoft Office caused by a use-after-free memory bug. An attacker who gets a user to open, or even preview, a specially crafted Office file could run code on that computer with the user's rights. Because the Preview Pane is an attack vector, the user may not even need to fully open the file.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can get a crafted Office file in front of a user could run code with that user's permissions and use it as a launch point for deeper attacks.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a use-after-free (CWE-416) in Microsoft Office. Office frees a block of memory while processing a document, but later code still tries to use it. A crafted file can control what ends up in that freed memory, which lets an attacker hijack the program's flow and run their own code. The attack needs no login and no special privileges. It does need user interaction, but that can be as small as viewing the file in the Preview Pane. Successful exploitation gives the attacker high impact on confidentiality, integrity, and availability within the user's context.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). An attacker sends or shares a crafted Office file and gets the user to open or preview it.

BUSINESS IMPACT: Office documents are the most common files in any business, and people open them without a second thought. A preview-pane attack makes this even riskier, since a user scrolling through email could trigger it. A successful attack can lead to stolen data, stolen credentials, ransomware, and lateral movement across the network, along with downtime, recovery costs, and reputational harm.

WORKAROUND: There are no official mitigations or workarounds for this vulnerability, so patching is the real fix. Until the update is in place, consider turning off the Preview Pane in Outlook and File Explorer, filter or quarantine Office attachments from unknown senders, keep Protected View on, and use attack surface reduction rules to stop Office from launching child processes.

URGENCY: Microsoft rates this flaw Critical with a CVSS score of 8.8. The Preview Pane attack path means very little user action is needed, no credentials are required, and Office is installed on nearly every business endpoint. That mix makes it a prime target for phishing campaigns once attackers study the patch. Roll out the Office update to all affected editions right away.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-110067 – Microsoft Office Word Remote Code Execution Vulnerability

“A Word document that looks harmless can become a doorway. Even the Preview Pane can open it, so one glance may be enough.”

This is a use-after-free flaw in Microsoft Word. An attacker can send a specially crafted Word document that, when handled a certain way, runs the attacker's code with the user's permissions. Microsoft notes that the Preview Pane is an attack vector, which means the risk is not limited to fully opening the file. The attacker does not need an account on the target system. Microsoft rates it Critical.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: A remote attacker could send a booby-trapped Word document and run code on the victim's computer with the victim's rights, giving them a foothold inside the organization.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-416, Use After Free. Word frees a block of memory and later uses it again, so an attacker who controls what fills that memory can hijack program flow. Microsoft describes a path where the user opens the crafted document, saves it as Rich Text Format, and dismisses the conversion and document-protection prompts. Microsoft also states that the Preview Pane is an attack vector. The CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: network, low complexity, no privileges, user interaction required, with high impact. Code runs with the permissions of the logged-in user.

EXPLOITABILITY: Affected: Microsoft 365 Apps for Enterprise (32-bit and 64-bit) and Microsoft Office LTSC 2021 and LTSC 2024 (32-bit and 64-bit). Fixes are delivered through the Office release channels. An attacker delivers the crafted document by email, file share, or download and relies on the user to handle it, or on the Preview Pane to render it.

BUSINESS IMPACT: Word documents are everywhere, and email attachments are still a favorite way in for attackers. A single user handling the wrong file could give an attacker code execution on a workstation, which is often the first step toward stealing data, deploying ransomware, or spreading across the network. If the user has admin rights, the damage grows quickly.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, consider turning off the Preview Pane for Office files, block or quarantine Word attachments from untrusted senders, keep users on least-privilege accounts, and remind staff not to open or convert unexpected documents.

URGENCY: This flaw is Critical, reachable over the network, needs no attacker account, and can be triggered through the Preview Pane. Office is installed on nearly every business desktop, so the exposed population is huge. Push the Office update across all channels now and confirm devices have picked it up.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-110047 – Microsoft Office Word Remote Code Execution Vulnerability

The most ordinary file in business, a Word document, can become an attacker's way into your network.

CVE-2026-110047 is a use-after-free flaw in Microsoft Office Word that lets an attacker run code on a user's computer. The user has to open a specially crafted Word file from the attacker. The Preview Pane is not an attack vector for this bug, but once the file is opened, the attacker's code runs with the user's permissions.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can get a document in front of a user can attempt this attack. If the user opens it, the attacker gains code execution with the user's rights.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The bug is a use-after-free (CWE-416) in Word. While processing a crafted document, Word frees an object in memory but later uses it again. An attacker can arrange for controlled data to sit in that freed memory and redirect the program to run their code. The attack is network-based with low complexity and no privileges needed, but it requires the user to open the file. The Preview Pane is not an attack vector. Success gives high impact to confidentiality, integrity, and availability.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). The attacker sends or shares a crafted Word file and convinces the user to open it.

BUSINESS IMPACT: Word files are shared everywhere, from invoices to resumes to contracts, so a malicious one is easy to disguise. A single opened document can give an attacker access to company data and credentials, and a base for ransomware or further attacks. HR, finance, and legal teams, who open outside documents often, are prime targets.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until patched, keep Protected View on, block Office files from untrusted sources, and remind users not to open unexpected attachments.

URGENCY: Word is on nearly every business computer, and malicious documents are one of the oldest and most reliable attack methods. The bug is Critical with no workaround. Even though the Preview Pane is not an attack vector, the patch should go out quickly.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-110043 – Microsoft Office Outlook Remote Code Execution Vulnerability

You don't even have to open it. Just previewing a poisoned email in Outlook could let an attacker in.

CVE-2026-110043 is a heap-based buffer overflow in Microsoft Office Outlook that lets an attacker run code on a user's computer. The attacker sends a specially crafted email, and the attack can trigger when the user selects the message to show it in the Preview Pane. The code runs with the user's permissions, and the attacker needs no account on the target system.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: Any remote attacker who can send email to a user can try this attack. If the user simply views the message in the Preview Pane, the attacker can run code and take over the user's session.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Outlook. When Outlook renders a crafted email, it writes more data into a heap buffer than it can hold, corrupting nearby memory. An attacker can use this corruption to run their own code. The Preview Pane is an attack vector, so the user only has to select the message for it to be displayed. The attack is network-based with low complexity and no privileges needed, and it brings high impact to confidentiality, integrity, and availability.

EXPLOITABILITY: Affected products are Microsoft 365 Apps for Enterprise (32-bit and 64-bit), Microsoft Office LTSC 2021 (32-bit and 64-bit), and Microsoft Office LTSC 2024 (32-bit and 64-bit). An attacker sends a crafted email and gets the user to select it so it shows in the Preview Pane.

BUSINESS IMPACT: Clicking through the inbox is something every employee does all day, and this bug turns that habit into a risk. A successful attack could expose email, files, and credentials, and give attackers a trusted account for sending more phishing. It can also be the first step toward ransomware or a wider breach.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until patched, consider turning off the Reading Pane, reading email in plain text, filtering suspicious mail at the gateway, and limiting local admin rights.

URGENCY: Preview Pane attacks need almost no help from the user, which makes them very appealing to attackers. Outlook is used across nearly every business, the bug is Critical, and there is no official workaround. Roll out the Office update quickly.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-114160 – Azure Managed Grafana Elevation of Privilege Vulnerability

“One forged request is all it takes. A cloud dashboard that fetches whatever an attacker asks for can hand over its own keys, and nobody has to log in or click a thing.”

This is a server-side request forgery (SSRF) flaw in Azure Managed Grafana, Microsoft's hosted version of the popular Grafana monitoring and dashboard service. An attacker with no account can trick the service into sending a request to a system the attacker controls. That request leaks a service access token, and with that token the attacker can act with whatever permissions the token carries. Microsoft rates it Critical and lists Customer Action Required as Yes.

CVSS Score: The CVSS v3.1 score does not exist for this vulnerability. Microsoft has not published a CVSS v3.1 Base Score or vector for it.

SEVERITY: Critical

THREAT: An unauthenticated remote attacker could steal a service access token from Azure Managed Grafana. With it, they could act with the token's permissions and reach cloud resources the service is trusted to touch.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-918, Server-Side Request Forgery. The service can be made to send outbound requests to an address chosen by the attacker instead of only to trusted destinations. When it does, it includes a service access token in that request, so the attacker's server simply receives the token. The attack works over the network, needs no authentication, and needs no user interaction. The impact is elevation of privilege: the attacker gains the rights tied to the stolen token, which in a cloud setting can extend well beyond the Grafana instance itself.

EXPLOITABILITY: Affected product: Azure Managed Grafana. The fix is described in the service release notes, and Microsoft marks no restart as required. An attacker exploits it by sending crafted input that makes the service call out to an attacker-controlled host, then capturing the token that comes with the request.

BUSINESS IMPACT: Grafana dashboards often sit next to the most sensitive parts of a cloud environment because they pull data from many sources. A stolen service token can turn a monitoring tool into a quiet entry point. Attackers could read operational data, query connected data sources, or move further into the Azure tenant using the token's rights. The result can be data exposure, tampering with monitoring, and a costly incident investigation.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the fix is confirmed in your instances, limit network exposure of the Grafana endpoint, review the permissions given to the service identity, and watch for unusual outbound requests and token use.

URGENCY: This flaw is rated Critical, needs no login, and needs no user action, which is the easiest attack path there is. Because Customer Action Required is Yes, teams should not assume the cloud provider handled it for them. Confirm your Azure Managed Grafana instances are on the fixed release and review the service identity's permissions now.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118737 – Remote Procedure Call Runtime Remote Code Execution Vulnerability

“No password, no click, no warning: a well-timed request could hand an attacker the keys to your server.”

CVE-2026-118737 is a remote code execution flaw in the Windows Remote Procedure Call (RPC) Runtime. It comes from improper verification of a cryptographic signature and lets an unauthenticated attacker run code over the network without any user action. Microsoft rates it Critical and it affects every supported version of Windows client and server.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated attacker with network access could send crafted requests to an affected server and run code on it, without needing any user to do anything.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is an improper verification of a cryptographic signature (CWE-347) in the Windows RPC Runtime, the component many Windows services use to talk to each other across a network. Microsoft describes a timing-dependent authentication weakness involving a pending DNS query: an attacker who wins the race can send specially crafted requests that the server accepts when it should not. Success lets the attacker run code on the server. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U) shows a network attack with no privileges or user action needed, but high complexity because of the race condition. Confidentiality, integrity and availability impacts are all high.

EXPLOITABILITY: Affected versions are Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2 (x64, ARM64 and 32-bit where applicable); and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An unauthenticated attacker on the network must win a race tied to a pending DNS query to get crafted RPC requests accepted.

BUSINESS IMPACT: RPC is woven into core Windows services, including those on domain controllers, file servers and application servers. A no-click, no-credential path to code execution on these systems is exactly what attackers want for spreading through a network. One compromised server could lead to stolen data, ransomware deployment and long business outages.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until patching is complete, block RPC traffic at the network edge, limit RPC access between network segments to the systems that need it, and monitor for unusual RPC activity.

URGENCY: This is a Critical, network-reachable remote code execution bug that needs no credentials and no user action. The race condition raises the bar, but it does not stop a determined attacker who can retry. With every supported Windows release affected, patch internet-facing and high-value servers such as domain controllers first. Fixes ship in the November cumulative updates, including KB5131291 (Windows 10 1607 and Server 2016), KB5131085 (Windows 10 1809 and Server 2019), KB5131096 (Windows 10 21H2/22H2), KB5131087 (Windows 11 23H2), KB5132061 and KB5132043 (Windows 11 24H2/25H2/26H2), KB5132059 (Windows 11 26H1), KB5131090 (Server 2022), and KB5131080 and KB5131077 (Server 2025). A restart is required.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118146 – Windows Active Directory Domain Services Remote Code Execution Vulnerability

“Any user, one crafted request, code running on your directory server. That is a bad day for the whole domain.”

CVE-2026-118146 is an incorrect authorization flaw in Active Directory Domain Services that leads to remote code execution. An authenticated attacker with low-level access can send a specially crafted request to an affected server and run code on it. No user interaction is needed, and exploitation is considered more likely.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: An authenticated attacker with low privileges could run code on an affected server and take control of it, putting the whole domain at risk.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is incorrect authorization (CWE-863) in Active Directory Domain Services. The service does not properly check whether a request is allowed, so a low-privileged user can send a crafted request that results in code running on the server. The attack is over the network, with low complexity, low privileges, and no user interaction. A successful attack has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. An attacker with a valid low-privileged account sends a specially crafted request to an affected server over the network.

BUSINESS IMPACT: Code execution on a directory server is one of the worst outcomes a business can face. Attackers can create accounts, reset passwords, push malware through Group Policy, and hold the entire network hostage. A single stolen user password could be enough to start the attack.

WORKAROUND: No official workarounds are listed. Restrict network access to domain controllers, enforce MFA and strong passwords to protect low-privileged accounts, and watch for unusual directory requests.

URGENCY: This is a Critical, low-complexity network bug in Active Directory, and exploitation is considered more likely. Stolen user credentials are cheap and common, so the bar to attack is low. Treat domain controllers as top priority for this update.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-118145 – Windows Function Discovery SSDP Provider Remote Code Execution Vulnerability

The service that helps Windows find printers and devices could also help an attacker on the same network find a way in.

CVE-2026-118145 is a use-after-free flaw in the Windows Function Discovery SSDP Provider, the component that discovers devices on the local network. An unauthenticated attacker on an adjacent network could exploit it to execute code. The attack is hard to pull off because it needs a memory allocation to fail while the service processes device information, but no credentials or user interaction are required.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An attacker on the same local network segment could run code on a Windows machine without logging in. This could help them spread from one compromised device to others nearby.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The bug is a use-after-free (CWE-416) in the Function Discovery SSDP Provider, which handles Simple Service Discovery Protocol traffic used to find devices. When the service processes device information, an allocation failure can leave it using memory that was already freed, which an attacker can exploit to run code. The CVSS vector is AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The attacker must be on an adjacent network, needs no privileges or user action, and faces high complexity because the allocation failure makes the attack harder to trigger reliably.

EXPLOITABILITY: Affected: Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. The attacker must be on the same network segment and send device information that the SSDP provider processes. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025).

BUSINESS IMPACT: Device discovery runs on many Windows systems by default, especially on laptops and desktops. An attacker who already has a foothold on one network device, or who joins a guest or Wi-Fi network, could use this flaw to move to other machines. That could speed up ransomware spread and data theft inside offices, branches, and shared networks.

WORKAROUND: Microsoft lists no mitigations or workarounds. If you cannot patch, consider disabling the SSDP Discovery and Function Discovery services where they are not needed, block SSDP traffic (UDP 1900) between segments, and keep untrusted devices on separate networks.

URGENCY: This is a Critical, unauthenticated code execution bug in a discovery service that is common on Windows endpoints. The need for adjacent network access and a failed allocation lowers the odds of attack, but it is a useful tool for lateral movement. Roll it out with your regular cumulative updates and do not delay, especially on laptops that join shared networks.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-116710 – Windows Message Queuing Remote Code Execution Vulnerability

One crafted packet, no password, no click. If Message Queuing is listening, attackers can knock on the door and walk right in.

CVE-2026-116710 is a heap-based buffer overflow in Windows Message Queuing (MSMQ). An unauthenticated attacker could send a specially crafted packet to an affected service over the network and run code on the target system. No login and no user interaction are needed. The attack is rated high complexity, but the reward is remote code execution on servers and workstations that have Message Queuing enabled.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: Any attacker who can reach the Message Queuing service over the network could run code on the target without credentials. That could give them a foothold for wider attacks.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The bug is a heap-based buffer overflow (CWE-122) in Windows Message Queuing. A specially crafted packet sent to the service can write past the end of a heap buffer, which can let an attacker take control of execution. The CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. It is network based and needs no privileges or user action. The complexity is high because success requires a deep understanding of the system and depends on the environment, configuration, and other security measures in place.

EXPLOITABILITY: Affected: Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. Systems are exposed when Message Queuing is running and reachable; an attacker sends a crafted packet to the service. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025).

BUSINESS IMPACT: Message Queuing often supports internal business applications, so it can sit on servers that handle orders, payments, or integration traffic. A successful attack could give an outsider code execution on those servers, leading to data theft, ransomware, or a pivot deeper into the network. Because no credentials are needed, the attack can start from anywhere on the network that can reach the service.

WORKAROUND: Microsoft lists no mitigations or workarounds. If you cannot patch, check whether the Message Queuing service is installed and disable it where it is not needed. Block inbound MSMQ traffic (TCP port 1801) at the firewall from untrusted networks.

URGENCY: This is a Critical, unauthenticated, network-reachable code execution bug. Message Queuing has a history of serious flaws, and exposed MSMQ services are easy to find. Patch systems with Message Queuing enabled first, and confirm the service is off where you do not need it.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-109459 – Windows Message Queuing Queue Manager Remote Code Execution Vulnerability

“No login, no click, just one crafted packet. If Message Queuing is listening, an attacker could be in.”

CVE-2026-109459 is a heap-based buffer overflow in the Windows Message Queuing (MSMQ) Queue Manager. An unauthenticated attacker can send a specially crafted packet to the service and run code on the target system without any user interaction. Attack complexity is high because the attacker must use complex memory shaping and needs specific conditions in place.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated remote attacker who can reach the MSMQ service could run code on the system and take full control of it.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in the MSMQ Queue Manager. A crafted network packet causes the service to write beyond a heap buffer, corrupting memory. With careful memory shaping, the attacker can turn this into code execution on the target. No authentication or user interaction is needed, but exploitation is harder because specific protocol settings or configurations must be in place. The impact on confidentiality, integrity, and availability is high.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. Only systems running the Message Queuing service are exposed. An attacker sends a crafted packet to the service over the network.

BUSINESS IMPACT: MSMQ often sits behind line-of-business apps, payment flows, and back-office integrations. A compromised queue server can give attackers a quiet path into critical business processes and the data moving through them. Because no login or user action is needed, a single exposed server could become an entry point for ransomware or data theft.

WORKAROUND: No official workarounds are listed. Check whether the Message Queuing service is enabled and disable it where it is not needed. Block MSMQ ports (such as TCP 1801) at the network edge and limit access to trusted hosts.

URGENCY: This is a Critical, unauthenticated, no-click network bug. Even with high attack complexity, servers running MSMQ are prime targets because a successful attack needs no help from users. Find your MSMQ systems and patch them first.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-125134 – Windows Function Discovery Resource Publication Remote Code Execution Vulnerability

“One overloaded Windows machine, one well-timed request from a nearby attacker, and the whole box belongs to someone else.”

CVE-2026-125134 is a use-after-free bug in the Windows Function Discovery Resource Publication service, the component that lets a Windows computer announce itself and its resources to other devices on the local network. An attacker on the same network segment, with no login and no help from a user, can send crafted SOAP requests to the service. If the system is short on memory and the attacker wins a timing race, the result is code running as SYSTEM. It is not easy to pull off, but when it works, the attacker gets full control of the machine.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An unauthenticated attacker on the same local network segment could take over a Windows system and run code with SYSTEM privileges. That gives them full control to steal data, install malware, or move on to other machines.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a use-after-free (CWE-416) in the Function Discovery Resource Publication service. When the service handles SOAP requests and a memory allocation fails under low-memory conditions, an asynchronous request-cleanup routine can free memory that is still in use. An attacker who sends specially crafted requests at the right moment can make the service reuse that freed memory, which can be shaped to hijack execution. Because the service runs with high privileges, successful exploitation leads to code execution as SYSTEM, with high impact on confidentiality, integrity, and availability. The attack needs no privileges and no user interaction, but the attack complexity is high because the target must be under sustained memory pressure and the attacker must win a timing condition.

EXPLOITABILITY: Affected systems include Windows 10 (versions 1607, 1809, 21H2, and 22H2), Windows 11 (versions 23H2, 24H2, 25H2, 26H1, and 26H2), and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. The attacker must be on an adjacent network, such as the same subnet or LAN segment. They send crafted SOAP requests to the service while the target is low on memory, either waiting for that state or trying to cause it.

BUSINESS IMPACT: Function Discovery is part of nearly every modern Windows desktop and server, so the attack surface is huge. An attacker who already has a foothold on an office network, guest Wi-Fi that is not properly separated, or a shared network segment could use this bug to grab SYSTEM control of nearby machines without a password. From there, they could steal sensitive data, deploy ransomware, harvest credentials, and spread across the network. A single compromised server could cause outages, data breaches, regulatory trouble, and costly recovery work.

WORKAROUND: There is no official workaround. If the update cannot be applied right away, limit exposure by keeping untrusted devices off internal network segments, separating guest and IoT networks, and blocking network discovery traffic between segments with host or network firewalls. Where network discovery is not needed, consider disabling the Function Discovery Resource Publication service. Watching for unusual memory pressure and service crashes may also help spot attempts.

URGENCY: Microsoft rates this bug Critical, and it gives an attacker SYSTEM-level control with no credentials and no user action. The tricky timing makes it harder to exploit, but attackers who are already inside a network are patient and well equipped. Because the affected service ships on almost every supported Windows desktop and server, the number of exposed machines is very large. Deploying this month's updates quickly closes a path that could turn one compromised device into a network-wide incident.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113865 – Windows Hyper-V Elevation of Privilege Vulnerability

“Hyper-V checks, then trusts, and an attacker slips in between. That tiny gap is enough to escape a virtual machine.”

CVE-2026-113865 is an elevation of privilege flaw in Windows Hyper-V. A time-of-check time-of-use (TOCTOU) race condition lets an attacker inside a guest virtual machine run code on the host in the context of the virtual machine worker process. The attacker needs low privileges in the guest and must win the race.

CVSS Score: 7.8

SEVERITY: Critical

THREAT: An attacker with low-level access inside a guest VM could escape to the Hyper-V host and run code as the virtual machine worker process. This puts the host and its other VMs within reach.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a time-of-check time-of-use race condition (CWE-367) in Windows Hyper-V. Hyper-V checks a value or resource, then uses it a moment later. An attacker in a guest VM can change that value in the gap between the check and the use, so Hyper-V acts on data it never validated. This can let the attacker run code on the host in the security context of the virtual machine worker process. The attack is local, needs low privileges and no user interaction, and the scope is changed. Attack complexity is high because the race must be won. Impact on confidentiality, integrity and availability is high.

EXPLOITABILITY: Affected versions include Windows 10 (versions 21H2 and 22H2, x64 and ARM64), Windows 11 (versions 23H2, 24H2, 25H2, 26H1 and 26H2), and Windows Server 2022 and 2025, including Server Core installations. An attacker with low privileges in a guest VM must win a race condition to exploit the bug.

BUSINESS IMPACT: Organizations rely on Hyper-V to keep workloads isolated from one another. A guest-to-host escape undermines that isolation and could let one compromised VM affect the host and every workload on it. The consequences include stolen data, tampered systems and outages across many services at once.

WORKAROUND: No official mitigations or workarounds are listed. Until you patch, limit access to guest VMs, separate untrusted workloads from sensitive ones, and monitor Hyper-V hosts for unusual behavior.

URGENCY: This flaw is rated Critical and breaks the boundary between guest and host. It is one of several Hyper-V escape bugs fixed this month, which makes Hyper-V hosts a clear patching priority. The race condition makes exploitation harder, but the reward for attackers is high. Deploy the update to Hyper-V hosts as soon as possible.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113864 – Windows Hyper-V Elevation of Privilege Vulnerability

“Hyper-V is the wall between your workloads. A use-after-free bug in that wall can turn an admin foothold into full SYSTEM control of the host.”

CVE-2026-113864 is a use-after-free flaw in Windows Hyper-V. An attacker who already has high-privileged local access can trigger the bug to elevate privileges on the system. Microsoft rates it Critical even though the base score is moderate, because Hyper-V sits at the core of virtualized infrastructure. The fix ships in the November 2026 security updates for supported Windows 10, Windows 11, and Windows Server releases.

CVSS Score: 6.4

SEVERITY: Critical

THREAT: A local attacker who already holds high privileges could exploit this flaw to gain elevated control over a Hyper-V system. On a virtualization host, that control can reach the workloads that depend on it.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The vulnerability is a use after free (CWE-416) in Windows Hyper-V. A use-after-free happens when code keeps using a block of memory after it has been released. An attacker who can control what gets placed in that freed memory may be able to steer the program into running their own code or corrupting trusted data. Here, an authorized local attacker can use the flaw to elevate privileges. The CVSS vector (AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H) shows a local attack with high complexity and high required privileges, but a successful exploit gives full impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected releases include Windows 10 Versions 1607, 1809, 21H2, and 22H2; Windows 11 Versions 23H2, 24H2, 25H2, 26H1, and 26H2 (x64 and ARM64); and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. The attacker must already be on the machine with high privileges and must win a hard-to-hit memory condition. No user interaction is needed.

BUSINESS IMPACT: Hyper-V hosts often run many business systems at once, so a flaw in the hypervisor puts more than one server at stake. An attacker who gains full control at this layer could read sensitive data, tamper with virtual machines, or shut down services. That can lead to outages, data breaches, and costly recovery work. It also gives an intruder a strong place to hide and to move deeper into the network.

WORKAROUND: Microsoft lists no workaround or mitigation. Until the update is applied, limit administrative access to Hyper-V hosts, remove the Hyper-V role from systems that do not need it, and watch hosts closely for unusual privileged activity.

URGENCY: Microsoft rates this flaw Critical, and it hits the virtualization layer that many organizations run on. The attack bar is high, since it needs local access with high privileges, but attackers who have already stolen admin credentials are exactly the ones who would use it. Hyper-V is common across Windows Server and Windows client fleets, so the exposure is broad. Patch Hyper-V hosts first, then roll the update out to the rest of the affected systems.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113862 – Windows Network Address Translation (NAT) Remote Code Execution Vulnerability

“A single crafted packet could turn the network plumbing of Windows into an attacker's front door.”

CVE-2026-113862 is a use-after-free bug in Windows Network Address Translation (NAT). An unauthenticated attacker could send a specially crafted packet over the network to run code on an affected system, with no user action needed. Microsoft rates it Critical and considers exploitation more likely.

CVSS Score: 8.1

SEVERITY: Critical

THREAT: An unauthenticated remote attacker could send a crafted packet to an affected system and run code on it without any user interaction.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known. Attackers are considered more likely to target it.

TECHNICAL SUMMARY: The flaw is a use after free (CWE-416) in the Windows NAT component, which translates network addresses as traffic moves between networks. When the component uses memory after it has been freed, an attacker who controls what fills that memory can redirect execution. Microsoft says an attacker must win a race condition, and that a specially crafted packet sent to an affected service can trigger code execution with no authentication or user interaction. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U) reflects a network attack with high complexity and high impact to confidentiality, integrity and availability.

EXPLOITABILITY: Affected versions are Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2 (x64, ARM64 and 32-bit where applicable); and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker sends crafted packets to an affected service and must win a race condition to trigger the use-after-free.

BUSINESS IMPACT: NAT sits in the path of network traffic, so a bug here can be reached without any login. Systems that route or share network connections, including hosts running virtualization or Internet Connection Sharing, are natural targets. A successful attack could give an outsider a foothold to move laterally, steal data or launch ransomware.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the update is applied, disable NAT or connection-sharing features where they are not needed, and restrict untrusted traffic to systems that use them.

URGENCY: This is a Critical, wormable-style bug: no credentials, no clicks, just packets. Microsoft considers exploitation more likely, and every supported Windows version is affected. Patch exposed and routing systems first, then the rest of the fleet. Fixes ship in the November cumulative updates, including KB5131291 (Windows 10 1607 and Server 2016), KB5131085 (Windows 10 1809 and Server 2019), KB5131096 (Windows 10 21H2/22H2), KB5131087 (Windows 11 23H2), KB5132061 and KB5132043 (Windows 11 24H2/25H2/26H2), KB5132059 (Windows 11 26H1), KB5131090 (Server 2022), and KB5131080 and KB5131077 (Server 2025). A restart is required.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113861 – Windows Hyper-V Elevation of Privilege Vulnerability

One bad guest can break the walls of the whole house. This Hyper-V flaw lets an attacker inside a virtual machine reach out and run code on the host itself.

CVE-2026-113861 is a use-after-free flaw in Windows Hyper-V. An attacker who already controls a guest virtual machine could use it to run code on the Hyper-V host in the context of the virtual machine worker process. That breaks the basic promise of virtualization: that what happens in one VM stays in that VM. Microsoft rates it Critical even though the attack is hard to pull off, because the payoff is control over the host that runs every other guest.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An attacker with high privileges inside a guest virtual machine could escape to the Hyper-V host. From there they could reach other virtual machines and the data they hold.

EXPLOITS: This vulnerability is not known to be exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The bug is a use-after-free (CWE-416) in Hyper-V, where the code keeps using memory after it has been freed. An attacker inside a guest VM can trigger this condition and steer what ends up in the freed memory, which can lead to code running on the host in the security context of the virtual machine worker process. The CVSS vector is AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H. The attack is local and needs high privileges in the guest, and the complexity is high because the attacker must win a race condition. The scope is changed, meaning the impact crosses from the guest into the host, with full loss of confidentiality, integrity and availability.

EXPLOITABILITY: Affected: Windows 10 versions 1607, 1809, 21H2 and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2; and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker needs high privileges inside a guest VM and must win a race condition to run code on the host. Fixes are delivered in the November cumulative updates: KB5131291 (Windows 10 1607 and Windows Server 2016), KB5131085 (Windows 10 1809 and Windows Server 2019), KB5131096 (Windows 10 21H2 and 22H2), KB5131087 (Windows 11 23H2), KB5132061 or KB5132043 (Windows 11 24H2, 25H2 and 26H2), KB5132059 (Windows 11 26H1), KB5131090 (Windows Server 2022), and KB5131080 or KB5131077 (Windows Server 2025).

BUSINESS IMPACT: Hyper-V hosts often carry dozens of workloads, so one compromised host can expose many servers at once. In shared or multi-tenant setups, a guest escape means one customer or department could reach another's data. Successful attacks could lead to data theft, tampering with other VMs, ransomware deployed at the hypervisor layer, and long outages for every service on that host.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you can patch, limit who has administrative access inside guest VMs, isolate untrusted workloads on separate hosts, and watch hosts for unusual worker process activity.

URGENCY: This is a Critical guest-to-host escape in a hypervisor that runs core business workloads. The race condition makes attacks harder, but it does not make them impossible, and the payoff is control of an entire host. Patch Hyper-V hosts first, especially those running untrusted or shared guests.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113860 – Windows Hyper-V Elevation of Privilege Vulnerability

“A race won in a split second could hand an ordinary user full administrator control. That is the danger of this Hyper-V flaw.”

CVE-2026-113860 is an elevation of privilege flaw in Windows Hyper-V. A use after free bug lets an attacker who already has low-level access to a system gain administrator privileges. To succeed, the attacker must win a race condition.

CVSS Score: 7.0

SEVERITY: Critical

THREAT: A local attacker with a standard user account could exploit this flaw to become an administrator. That level of access lets them disable defenses, steal data and spread further.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a use after free (CWE-416) in Windows Hyper-V. Hyper-V can keep using a block of memory after it has been released. If an attacker manages to place their own data in that freed memory at the right moment, they can influence what Hyper-V does next and raise their privileges. The attack is local, needs low privileges and no user interaction, and the scope is unchanged. Attack complexity is high because the attacker must win a race condition. A successful attack grants administrator privileges, with high impact on confidentiality, integrity and availability.

EXPLOITABILITY: Affected versions include Windows 10 (versions 1809, 21H2 and 22H2), Windows 11 (versions 23H2, 24H2, 25H2, 26H1 and 26H2), and Windows Server 2019, 2022 and 2025, including Server Core installations. An attacker with local, low-privileged access must win a race condition to exploit the bug.

BUSINESS IMPACT: Elevation of privilege bugs are the second step in most real attacks. Once an attacker lands on a machine through phishing or stolen credentials, a flaw like this lets them become an administrator, turn off security tools, dump credentials and move across the network. On Hyper-V hosts, administrator access can put every hosted workload at risk.

WORKAROUND: No official mitigations or workarounds are listed. Until you patch, limit local logon rights on Hyper-V systems, follow least privilege, and watch for unexpected privilege changes.

URGENCY: This flaw is rated Critical and affects Hyper-V across a wide range of Windows client and server versions. The race condition makes exploitation harder, but privilege escalation bugs are prized by attackers who already have a foothold, and they are often chained with other flaws. Include this update in your standard rollout and prioritize Hyper-V hosts and shared systems.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113856 – Windows Hyper-V Elevation of Privilege Vulnerability

“A memory overflow inside a virtual machine should stay inside the virtual machine. This one spills over onto the host.”

CVE-2026-113856 is an elevation of privilege flaw in Windows Hyper-V. A heap-based buffer overflow lets an attacker inside a guest virtual machine run code on the host in the context of the virtual machine worker process. The attacker needs low privileges in the guest and must win a race condition.

CVSS Score: 7.8

SEVERITY: Critical

THREAT: An attacker with a foothold inside a guest VM could break out and run code on the Hyper-V host under the virtual machine worker process. That gives them a path from one VM toward the host and its other workloads.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in Windows Hyper-V. Hyper-V can write more data into a heap buffer than it can hold, which overwrites nearby memory. An attacker in a guest VM can use this to run code on the host in the security context of the virtual machine worker process. The attack is local, needs low privileges and no user interaction, and the scope is changed, which means the impact reaches beyond the guest. Attack complexity is high because the attacker must win a race condition. Impact on confidentiality, integrity and availability is high.

EXPLOITABILITY: Affected versions include Windows 10 (versions 21H2 and 22H2), Windows 11 (versions 23H2, 24H2, 25H2, 26H1 and 26H2), and Windows Server 2022 and 2025, including Server Core installations. An attacker with low privileges in a guest VM must win a race condition to trigger the overflow.

BUSINESS IMPACT: Virtualization keeps workloads apart. When a guest can run code on the host, a single compromised VM can threaten every other system on that host. This matters most for shared hosts, test labs that run untrusted code, and environments that host workloads for different customers or departments. The result could be data exposure, service disruption or a wider breach.

WORKAROUND: No official mitigations or workarounds are listed. Until you patch, restrict who can run code in guest VMs, avoid placing untrusted VMs on hosts with sensitive workloads, and monitor hosts for unusual worker process activity.

URGENCY: This flaw is rated Critical and lets an attacker cross from a guest VM to the host, which is one of the most serious kinds of virtualization bugs. Only low privileges are needed inside the guest. The race condition adds difficulty, but attackers who target virtual environments have the time and skill to work through it. Patch Hyper-V hosts on Windows Server 2022 and 2025 and supported clients promptly.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113859 – Windows TCP/IP Remote Code Execution Vulnerability

“No login, no click, just network traffic: a flaw in the Windows TCP/IP stack lets a nearby attacker reach straight into the system.”

CVE-2026-113859 is a remote code execution flaw in the Windows TCP/IP stack. A use after free bug lets an unauthenticated attacker on an adjacent network run code on the target system. The attacker must win a race condition, but needs no credentials and no user interaction.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An attacker on the same local network segment could run code on a vulnerable Windows system without logging in. That gives them control of the machine and a base for further attacks.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.

TECHNICAL SUMMARY: The flaw is a use after free (CWE-416) in Windows TCP/IP, the core networking stack in Windows. Under certain timing, the stack can use memory after it has been freed. An attacker who sends crafted network traffic and wins the race can place controlled data in that memory and redirect execution to run code. The attack vector is adjacent, so the attacker must be on the same network segment. It needs no privileges and no user interaction, and the scope is unchanged. Attack complexity is high because a race condition must be won. Impact on confidentiality, integrity and availability is high.

EXPLOITABILITY: Affected versions are Windows 11 versions 24H2, 25H2, 26H1 and 26H2 (x64 and ARM64) and Windows Server 2025, including Server Core installations. An attacker on an adjacent network must send crafted traffic and win a race condition.

BUSINESS IMPACT: TCP/IP is part of every networked Windows system, so the exposure is broad on affected versions. An attacker who gets onto a shared network, such as an office LAN, guest Wi-Fi or a compromised device, could take over systems without any credentials. Code execution in the networking stack could lead to data theft, system takeover or crashes that disrupt operations.

WORKAROUND: No official mitigations or workarounds are listed. Until you patch, segment networks to limit who can reach critical systems, keep untrusted devices off networks shared with servers, and watch for unusual network activity.

URGENCY: This flaw is rated Critical and sits in the Windows networking stack, which every affected system uses. It needs no credentials and no user action, only a position on the local network. The race condition and adjacent-network requirement narrow the attack, but newer Windows 11 releases and Windows Server 2025 are being deployed widely. Roll out the update quickly, especially on servers and laptops that join shared networks.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113825 – Windows SMB Server Network Transport Driver (srvnet.sys) Remote Code Execution Vulnerability

Win the race, own the server: a timing bug in the Windows SMB driver could hand attackers remote code execution.

CVE-2026-113825 is a Critical remote code execution vulnerability in the Windows SMB Server Network Transport Driver, srvnet.sys. It is caused by a race condition, where two operations use the same shared resource without proper synchronization. An authenticated attacker who wins that race could run code on the target over the network. The bug affects Windows 10 version 1809 and later, Windows 11, and Windows Server 2019, 2022, and 2025.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An attacker with low-level network credentials could send crafted SMB traffic to a vulnerable system and, if they win a race condition, run code in the kernel-level SMB driver.

EXPLOITS: This vulnerability is not known to be exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is identified.

TECHNICAL SUMMARY: The vulnerability is a race condition (CWE-362) in srvnet.sys, the kernel-mode driver that handles network transport for the Windows SMB server. When concurrent operations touch a shared resource without proper locking, an attacker can time requests so that memory is used in an unsafe state. Exploiting it successfully can lead to code execution on the target. The CVSS v3.1 vector is AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. The attack comes over the network, needs low privileges, and needs no user interaction, but attack complexity is high because the attacker must win the race. Successful exploitation has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2019, 2022, and 2025, including Server Core installations. An authenticated attacker would send repeated, carefully timed SMB requests to the target to win the race condition.

BUSINESS IMPACT: SMB is the backbone of Windows file sharing, and file servers often hold an organization's most important data. Code execution in the SMB transport layer could let an attacker take over file servers and domain-joined systems, steal or encrypt shared data, and spread across the network. Because only low privileges are needed, a single phished user account could be enough to start the attack.

WORKAROUND: No official mitigation or workaround is listed, so install the update. In the meantime, block TCP port 445 at the network perimeter, restrict SMB access between network segments to systems that truly need it, and use host firewalls to limit which machines can reach SMB on servers and workstations.

URGENCY: This flaw is rated Critical, sits in a kernel-level network driver, and affects nearly every modern Windows system that shares files. The race condition raises the bar, but low privileges and no user interaction keep the attack path realistic for anyone already inside the network. File servers and domain systems should be patched first, and the update requires a restart.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113753 – Windows Hyper-V Elevation of Privilege Vulnerability

“When Hyper-V trusts a pointer it should not, an admin can reach into the most protected part of Windows, the place built to stay off-limits even to admins.”

This vulnerability is in Windows Hyper-V on Windows 11 version 26H1. Hyper-V follows a pointer it should not trust, and an attacker who already has high privileges can use it to gain Virtual Trust Level 1 (VTL1) privileges. VTL1 is the isolated, higher-trust environment that powers virtualization-based security features, so this flaw targets one of Windows' strongest protections. Microsoft rates it Critical.

CVSS Score: 8.2

SEVERITY: Critical

THREAT: A local attacker with high privileges could break into VTL1, the protected environment that guards secrets and security checks, and gain control that normal administrators are not supposed to have.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-822, Untrusted Pointer Dereference. Hyper-V takes a pointer value from a less trusted source and uses it without proper checks, which can let an attacker make Hyper-V read or write memory of the attacker's choosing. Microsoft states that successful exploitation grants VTL1 privileges. The CVSS vector is AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H: local, low complexity, high privileges required, no user interaction, and a changed scope with high impact across confidentiality, integrity, and availability. Low complexity makes this more practical than many Hyper-V bugs once an attacker is an admin.

EXPLOITABILITY: Affected: Windows 11 version 26H1 for x64 and ARM64 systems. The fix is KB5132059, and a restart is required. An attacker must already have high privileges on the machine and then trigger the bad pointer use in Hyper-V.

BUSINESS IMPACT: Virtualization-based security exists to protect credentials and enforce code integrity even when an admin account is compromised. If an attacker can reach VTL1, those protections can no longer be trusted. That opens the door to credential theft, persistent hidden access, and bypassing core security controls. For organizations that rely on these features to stop credential theft, this turns a bad day into a much worse one.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until you patch, tightly limit local administrator access and watch privileged accounts for unusual activity.

URGENCY: This is a Critical flaw with low attack complexity that defeats a protection layer designed to survive admin compromise. Attackers who gain admin rights through phishing or another bug could chain it to go deeper. Deploy KB5132059 to Windows 11 26H1 devices promptly and plan for the required restart.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113752 – Windows Print Spooler Components Remote Code Execution Vulnerability

“The Print Spooler is back in the spotlight. One won race on the local network could hand an attacker your system.”

CVE-2026-113752 is a use-after-free bug in Windows Print Spooler components. An unauthenticated attacker on the same adjacent network can exploit it to run code on the target system. To succeed, the attacker must win a race condition, which makes the attack harder.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An unauthenticated attacker on the local or adjacent network could run code on the target system and take control of it.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a use-after-free (CWE-416) in Print Spooler components. Windows frees a block of memory but keeps using it, so an attacker who controls what fills that memory can hijack execution. The attacker must win a race condition to time this correctly. The attack vector is adjacent network, with high complexity, no privileges, and no user interaction. A successful attack has high impact on confidentiality, integrity, and availability.

EXPLOITABILITY: Affected versions include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. An attacker on the same network segment sends crafted requests to the spooler and tries to win the race to trigger the bug.

BUSINESS IMPACT: The Print Spooler runs by default on most Windows systems, including servers that never print. A successful attack inside the network lets an intruder spread from machine to machine, steal data, or deploy ransomware. Past spooler bugs have shown how fast attackers jump on this service.

WORKAROUND: No official workarounds are listed. Where printing is not needed, especially on domain controllers and servers, stop and disable the Print Spooler service. Segment networks to limit who can reach spooler services.

URGENCY: This is a Critical bug that needs no login and no user action. The Print Spooler is on almost every Windows system, so the exposure is wide. Even with a race condition to win, attackers already on the network have time to try, so patch soon.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-113749 – Microsoft Windows Codecs Library Remote Code Execution Vulnerability

“One poisoned media file is all it takes. A flaw buried in the code Windows uses to read images and video can hand an attacker full control of the machine.”

CVE-2026-113749 is a heap-based buffer overflow in the Microsoft Windows Codecs Library, the part of Windows that decodes images, audio, and video. An integer overflow in how the library sizes its memory can lead it to write past the end of a heap buffer. A remote attacker with no account on the target can use this to run code, but only after a user opens or processes a specially crafted file. The bug affects a wide range of supported Windows 10, Windows 11, and Windows Server releases.

CVSS Score: 7.5

SEVERITY: Critical

THREAT: An unauthenticated remote attacker who tricks a user into opening or previewing a malicious media file could run code on the system and take over the user's session, with full impact on confidentiality, integrity, and availability.

EXPLOITS: This vulnerability is not known to be actively exploited. The issue was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw sits in the Windows Codecs Library, which parses and decodes media content for Windows apps and system components. When the library handles certain values in a crafted file, an integer overflow or wraparound (CWE-190) can produce a buffer that is too small for the data that follows. The decoder then writes beyond that heap buffer (CWE-122), corrupting nearby memory. An attacker who shapes this corruption carefully can redirect execution and run code in the context of the process doing the decoding. The attack works over the network, needs no privileges, but does need user interaction, and attack complexity is high: success depends on a deep understanding of the target and on factors such as system configuration and other security defenses.

EXPLOITABILITY: Affected systems include Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2; and Windows Server 2016, 2019, 2022, and 2025, including Server Core installations. An attacker would deliver a crafted media file through email, a website, a chat app, or a file share and convince a user to open it. Exploitation is rated less likely because of the high attack complexity.

BUSINESS IMPACT: Media files are everywhere, and people open them without a second thought, which makes this an easy lure for phishing campaigns. A successful attack gives an outsider code execution on a workstation or server, opening the door to data theft, ransomware deployment, credential harvesting, and lateral movement across the network. Because the codecs library ships in almost every supported version of Windows, the exposed footprint in a typical organization is large, and one compromised endpoint can become the starting point for a much wider breach.

WORKAROUND: No official mitigation or workaround is listed. Until the update is installed, block or quarantine untrusted media attachments at the email and web gateway, remind users not to open unexpected image or video files, and limit user privileges to reduce what an attacker gains if code runs.

URGENCY: This flaw carries a Critical rating, needs no credentials, and can be triggered remotely through something as ordinary as a media file. The high complexity and lack of known exploitation buy some time, but not much: once a patch is out, attackers study it, and a bug in a component present on nearly every Windows device is an attractive target. Prioritize this update across workstations first, where users open files, and then servers.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-112967 – Windows Xbox Live Networking Service Remote Code Execution Vulnerability

No click, no login, no warning. An attacker on your network could reach out and run code on your Windows machines.

CVE-2026-112967 is a heap-based buffer overflow in the Windows Xbox Live Networking Service that allows an attacker to run code remotely. An attacker on the same network can call service endpoints and trigger the bug without any credentials and without any action from the user. It affects a wide range of Windows 10 and Windows 11 versions.

CVSS Score: 9.8

SEVERITY: Critical

THREAT: An attacker with access to the same network can exploit this flaw without credentials or user interaction. A successful attack could give them full control of the affected Windows system.

EXPLOITS: This vulnerability is not known to be actively exploited. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The flaw is a heap-based buffer overflow (CWE-122) in the Windows Xbox Live Networking Service. When the service handles calls to its endpoints, it can write past the end of a heap buffer. An in-network attacker who calls arbitrary endpoints with crafted input can corrupt memory and gain remote code execution. The attack is network-based, has low complexity, and needs no privileges or user interaction. This gives the highest possible impact on confidentiality, integrity, and availability, which is why it scores 9.8.

EXPLOITABILITY: Affected systems include Windows 10 Version 1809, 21H2, and 22H2, and Windows 11 Version 23H2, 24H2, 25H2, 26H1, and 26H2, across 32-bit, x64, and ARM64 editions where listed. Fixes ship in KB5131085, KB5131096, KB5131087, KB5132061, KB5132043, and KB5132059, depending on the version. Most of these updates need a restart. An attacker on the network sends crafted calls to the service's endpoints.

BUSINESS IMPACT: This is the kind of bug that turns one compromised device into a network-wide problem. Because no user action is needed, an attacker who gets a foothold anywhere on the internal network could jump from machine to machine on their own. That opens the door to fast-moving ransomware, data theft, and business shutdown. The service name sounds consumer-focused, but it lives on standard business Windows endpoints.

WORKAROUND: Microsoft lists no mitigations or workarounds. If you cannot patch right away, limit network access between workstations, segment the network, and consider disabling the Xbox Live Networking Service on business systems that do not need it, after testing.

URGENCY: A CVSS score of 9.8, no login, and no user interaction make this the most urgent fix in this group. It affects nearly every supported Windows client version, and network-reachable, wormable-style bugs are a top target for attackers. Patch all Windows 10 and Windows 11 systems right away and plan for the required restarts.

See more details about this CVE

[2] Critical – Same Day Deployment CVE-2026-114169 – Windows Raw Image Extension Remote Code Execution Vulnerability

“You do not even have to open the photo. Just browsing to the wrong folder can let a poisoned RAW image run code on your PC.”

This is a heap-based buffer overflow in the Windows Raw Image Extension, the add-on that lets Windows display camera RAW photos. An attacker can create a malicious RAW image file, and the bug can trigger when Windows generates a thumbnail or preview of it. The user only has to navigate to the folder that holds the file; they do not need to open it. Successful exploitation allows remote code execution. Microsoft rates it Critical.

CVSS Score: 8.8

SEVERITY: Critical

THREAT: A remote attacker could plant a malicious RAW image where a user will browse to it and run code on that user's computer without the file ever being opened.

EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept exploit code is known.

TECHNICAL SUMMARY: The weakness is CWE-122, Heap-based Buffer Overflow. When the Raw Image Extension parses a crafted RAW file, it writes data past the end of a heap buffer, which can corrupt memory and let the attacker take control of execution. Because Windows builds thumbnails and previews automatically, simply viewing a folder in File Explorer can trigger the parsing. The CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: network, low complexity, no privileges, user interaction required, with high impact.

EXPLOITABILITY: Affected: Raw Image Extension on Windows 10 versions 1809, 21H2, and 22H2, and on Windows 11 versions 23H2, 24H2, 25H2, 26H1, and 26H2. The fix is delivered as an updated Raw Image Extension, and no restart is required. An attacker places a crafted RAW file in a folder, download, or share and convinces the user to browse to it.

BUSINESS IMPACT: Image files feel safe, and users rarely think twice about opening a folder of photos. That makes this an easy lure through shared drives, downloads, or removable media. A successful attack gives the attacker code execution on the workstation, which can lead to credential theft, data loss, and a path into the wider network.

WORKAROUND: Microsoft lists no mitigations or workarounds. Until the extension is updated, consider removing the Raw Image Extension where it is not needed, and avoid browsing untrusted folders that may contain RAW image files.

URGENCY: This flaw is Critical, needs no privileges, and can trigger just from viewing a folder. The extension is installed on a wide range of Windows 10 and Windows 11 builds. Make sure the updated Raw Image Extension reaches all devices, especially since app-based updates are easy to overlook in normal patch cycles.

See more details about this CVE

Webinar Recording: November 2026 Vulnerability Digest from Action1

See What You Can Do with Action1

 

Join our weekly LIVE demo “Patch Management That Just Works with Action1” to learn more

about Action1 features and use cases for your IT needs.

 

spiceworks logo
getapp logo review
software advice review
trustradius
g2 review
g2 review