🔍 Read the full analysis: CISA Sets November 24 Deadline For Outlook Zero-Day: What To Do on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
CISA added Outlook vulnerability CVE-2026-124194 to its Known Exploited Vulnerabilities catalog on Nov. 10, citing evidence of active exploitation. Federal civilian agencies must apply the vendor fix by Nov. 24; Microsoft says opening a crafted file can expose a user’s NTLMv2 hash, and lists no workaround.
The US Cybersecurity and Infrastructure Security Agency has set a Nov. 24, 2026, deadline for federal civilian agencies to address an Outlook vulnerability that Microsoft says attackers are already exploiting. The flaw, CVE-2026-124194, can expose a user’s NTLMv2 hash when the user opens a specially crafted file, according to Microsoft’s security advisory; Microsoft lists an Office update as the fix and no workaround.
CISA added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog on Nov. 10, saying the entries added that day were included “based on evidence of active exploitation.” The catalog requires federal civilian executive branch agencies to apply vendor mitigations by the listed due date. CISA’s directive says agencies should discontinue use of a product if mitigations are unavailable; Microsoft has released updates for affected Office products.
Microsoft describes the issue as a spoofing vulnerability. An unauthenticated attacker can send a crafted file and try to persuade a person to open it in an affected Outlook version. Microsoft says opening the file may cause Outlook to connect to an attacker-controlled network location without the usual external-content warning, disclosing the user’s NTLMv2 hash. The company says an attacker could use that information to authenticate as the user.
Microsoft rates the flaw Moderate, with a CVSS score of 6.5 out of 10. The attack requires a user to open the file, but Microsoft says the Preview Pane is not an attack vector. The supplied source lists fixed builds for Office LTSC 2021 and 2024 as 16.0.14334.21048 and 16.0.17932.21140, respectively. Microsoft 365 Apps users should consult Microsoft’s Nov. 10 security release for the fixed build that applies to their update channel.
Outlook Zero-Day Patch by November 24
CISA reports active exploitation of an Outlook flaw that can expose a user’s NTLMv2 hash. Apply Microsoft’s fix and verify the installed build.
How exposure happens
A user must open a specially crafted file in an affected Outlook version.
An attacker tries to persuade a user to open it.
It may connect to an attacker-controlled network location without the usual external-content warning.
Microsoft says the NTLMv2 hash could be used to authenticate as the user.
Who must act by the deadline?
CISA’s binding date applies to federal civilian executive branch agencies.
- Apply the vendor update by Nov. 24, 2026.
- Verify affected Office installations run a fixed build.
- The cited directive does not bind them to that date.
- CISA encourages prioritizing KEV vulnerabilities.
Apply and verify the fix
Match installed versions to Microsoft’s guidance for the relevant product and update channel.
| Product | Fixed build or guidance |
|---|---|
| Office LTSC 2021 | 16.0.14334.21048 |
| Office LTSC 2024 | 16.0.17932.21140 |
| Microsoft 365 Apps | Check the Nov. 10 release for the applicable channel build |
What remains unknown
Public descriptions confirm reported exploitation but leave key incident details unanswered.
- Who is behind the attacks and who was targeted.
- How many users may be affected or when exploitation began.
- Whether any victim’s account or network was accessed using a stolen hash.
Why the Outlook Hash Exposure Matters
The exposed hash can create a risk beyond the initial Outlook message. Microsoft says attackers could use it to authenticate as the affected user; in an organization, that could give an attacker a route toward other accounts or systems, depending on the environment and the protections in place. The source material does not establish that such follow-on access occurred in these attacks.
The flaw is not described as an automatic, worm-like attack: a user must open the file. But that requirement does not remove the urgency. Microsoft marks exploitation as detected, and CISA’s KEV listing reflects evidence of active exploitation. Updating Office closes the identified vulnerability; organizations should not treat the federal deadline as a reason to wait if they can apply the update sooner.
The Nov. 24 date is a binding requirement for federal civilian executive branch agencies, not a universal legal deadline for private companies or other organizations. CISA separately encourages all organizations to prioritize KEV vulnerabilities through risk-based vulnerability management, making the date a useful signal for defenders outside government as well.
Products Worth Considering

Apple Watch Ultra 4 GPS + Cellular, 49 mm

Bose Smart Ultra Dolby Atmos Soundbar

Bose QuietComfort Wireless Noise-Cancelling Headphones, Petal Pink
As an affiliate, we earn on qualifying purchases.
How the Federal Deadline Applies
CISA’s Nov. 10 alert added six vulnerabilities to the KEV catalog, including this Outlook issue and flaws affecting products from Cisco, Barracuda Networks, Openwave and Google Chromium. The catalog entry directs agencies to apply vendor instructions by Nov. 24, 2026. CISA says its binding directive applies only to federal civilian executive branch agencies, while encouraging other organizations to prioritize catalog vulnerabilities.
Microsoft’s entry identifies Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024, in both 32-bit and 64-bit editions, as affected. The source material lists the fixed LTSC builds above and points Microsoft 365 Apps administrators to the Nov. 10 release, which gives version and build numbers by channel. Administrators should verify the installed build against Microsoft’s applicable channel guidance rather than assume that an update policy means a device has already received the fix.
“An unauthenticated attacker could send a specially crafted message file and convince a user to open it in an affected version of Microsoft Outlook.”
— Microsoft Security Update Guide
What Is Still Unknown About Attacks
The supplied reporting does not identify who is behind the attacks, which organizations or users were targeted, how many may have been affected, or when exploitation began. Microsoft and CISA’s public descriptions establish that exploitation is reported, but they do not provide those details.
CISA’s catalog lists ransomware use as unknown. Its entry also does not mark the flaw for forensic triage under the directive’s field for checking whether attackers accessed systems before patching. That designation is not proof that no compromise occurred. The available information does not say whether any specific victim’s account or network was accessed using a stolen hash.
Patch Before the November Deadline
Federal civilian agencies should apply Microsoft’s update by Nov. 24 and verify that affected Office installations are running a fixed build. Microsoft 365 Apps administrators need to match installed versions to the relevant update channel in Microsoft’s Nov. 10 release. The source material lists no workaround, so organizations should not rely on a temporary configuration change in place of updating.
Other organizations are not bound by this CISA directive, but should prioritize the update in light of the active-exploitation listing. Further details about the attackers, targets and scale of exploitation remain unavailable in the cited material; any additional public guidance or incident information could clarify those questions.
Key Questions
What is CVE-2026-124194?
It is a Microsoft Outlook spoofing vulnerability. Microsoft says opening a specially crafted file in an affected Outlook version can prompt a connection to an attacker-controlled location and disclose the user’s NTLMv2 hash.
Who must meet the Nov. 24 deadline?
The deadline applies to US federal civilian executive branch agencies under the CISA directive. CISA encourages other organizations to prioritize KEV vulnerabilities, but the cited directive does not make the date binding on them.
What should organizations do to fix the flaw?
Install the applicable Microsoft Office security update and confirm the installed build. Microsoft lists fixed builds for Office LTSC 2021 and 2024 and provides channel-specific Microsoft 365 Apps builds in its Nov. 10 release. The source material lists no workaround.
Can the flaw be triggered just by using Outlook’s Preview Pane?
Microsoft says the Preview Pane is not an attack vector. Its description says a user must be convinced to open a specially crafted file.
What is not yet known about the exploitation?
The available source material does not identify the attackers, targets, number of affected users or start date of exploitation. It also lists use in ransomware campaigns as unknown.
Source: ThorstenMeyerAI.com
