← All insights
Security Advisory6 min read

Outlook and Chrome Zero-Days: Patch Both Now

An exploited Outlook flaw leaks Windows password hashes when a user opens a file. Chrome has an exploited flaw too. Fixed builds and what to check.

Advisory at a glance

highCVSS 6.5 for the Outlook flaw (Microsoft rates it Moderate). Google rates the Chrome flaw High.Actively exploited
Affected
Outlook in Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 before the November 10, 2026 updates. Google Chrome before 157.0.8103.50.
Fixed in
Office LTSC 2021 build 16.0.14334.21048, Office LTSC 2024 build 16.0.17932.21140, and for Microsoft 365 Apps the build Microsoft lists for your update channel. Chrome 157.0.8103.50 or later.
What to do
Confirm the November Office updates and the current Chrome and Edge versions are installed on every computer, then tell staff not to open unexpected message files.
On this page
  1. The short version
  2. What the Outlook flaw does
  3. Why a 6.5 deserves urgency
  4. The Chrome flaw
  5. The rest of the November release
  6. What to do
  7. How we help
  8. Sources

Field notes from the engineering team

Two software flaws that attackers are already using were fixed last week, in programs most offices run every day. On November 10, 2026, Microsoft’s Patch Tuesday fixed CVE-2026-124194, a flaw in Outlook that leaks a user’s Windows password hash. On November 9, Google fixed CVE-2026-125350 in Chrome. CISA added both to its Known Exploited Vulnerabilities (KEV) catalog on November 10.

Microsoft fixed more than 1,000 vulnerabilities this month, so it is easy to treat the whole release as noise. The two items below are the ones to act on first.

The short version

ItemDetail
Outlook flawCVE-2026-124194. Opening a crafted message file makes Outlook connect to an attacker’s server without the usual external-content warning, which hands over the user’s NTLMv2 password hash. Microsoft rates it Moderate, CVSS 6.5.
Chrome flawCVE-2026-125350. A use-after-free bug in Chrome’s XML component, rated High by Google.
Exploited?Yes, for both. Microsoft lists the Outlook flaw as exploited and not publicly disclosed before the fix. Google says an exploit for the Chrome flaw exists in the wild.
AffectedOutlook in Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024. Chrome before 157.0.8103.50.
FixThe November 10 Office updates, and Chrome 157.0.8103.50 or later.
CISA deadlineNovember 24, 2026 for federal agencies. CISA encourages every organization to treat KEV entries as a priority.

What the Outlook flaw does

Microsoft’s advisory describes the attack in three steps. An attacker sends a specially crafted message file. A user opens it. Outlook then connects to a network location the attacker controls, and it does so without showing its usual external-content warning.

That connection is the problem. Microsoft says it discloses the user’s NTLMv2 hash, a Windows password credential, and that the attacker could use it to authenticate as the user.

Two details limit the risk. The user has to open the file, and Microsoft says the Preview Pane is not an attack vector. The advisory we read does not describe who was attacked or how widely.

Why a 6.5 deserves urgency

A CVSS 6.5 score looks routine. The score reflects that the bug steals a hash and runs no code. It does not reflect that attackers are using it.

Rapid7 explains what an attacker can do with the hash. They can relay it live to another service and sign in as the user, where that service does not require safeguards such as SMB signing, LDAP signing, or Extended Protection for Authentication on Exchange and Active Directory Certificate Services. Or they can crack the hash offline and recover the password itself. Rapid7 notes the flaw is useful both for broad credential harvesting and for targeted attacks.

For a small organization, the plain version is this. One person opening one attachment can give an attacker that person’s login, and the login may reach mail, file shares and remote access.

The Chrome flaw

Google’s November 9 stable channel update moved Chrome to 157.0.8103.50 or .51 on Windows and Mac and 157.0.8103.50 on Linux. It included nine security fixes. Google’s note says it is aware that an exploit for CVE-2026-125350 exists in the wild. CISA lists it as a Chromium use-after-free vulnerability.

Microsoft Edge is built on Chromium. Our advice is to confirm that Edge has taken the matching fix as well. We have not confirmed Edge’s fixed version number, so check Microsoft’s Edge security release notes for it.

The rest of the November release

Microsoft’s other fixes this month did not include exploited bugs, but several are serious for servers. Microsoft’s own data lists these, none marked as exploited:

  • CVE-2026-116928, Windows Search remote code execution, CVSS 9.8, Critical. Rapid7 explains that on a server running Exchange, the Windows Search component indexes email, so a malicious attachment could trigger it. The fix is a Windows update, not an Exchange update.
  • CVE-2026-119952, Windows Schannel (Microsoft’s TLS component) remote code execution, CVSS 8.1, Critical. Microsoft assesses exploitation as more likely.
  • CVE-2026-85844, Windows Kerberos elevation of privilege, CVSS 9.8, rated Important.
  • CVE-2026-119958, Windows LDAP remote code execution, CVSS 9.8, Critical.

Rapid7 also notes that as of November 11, the 23H2 Enterprise, Education and IoT editions of Windows 11 are past their end dates.

What to do

1. Confirm the Office update is installed. The fixed builds are 16.0.14334.21048 for Office LTSC 2021 and 16.0.17932.21140 for Office LTSC 2024. For Microsoft 365 Apps for Enterprise, the fixed build depends on your update channel. Microsoft lists them on its Microsoft 365 Apps security updates page. In Outlook, go to File, Office Account, and read the version and build number. Our advice: do not rely on automatic updates alone, and check every computer.

2. Update Chrome and Edge, and restart them. In Chrome, open the menu, then Help, then About Google Chrome. The page starts the update, and Chrome asks you to relaunch. You need version 157.0.8103.50 or later. Do the same check on Edge.

3. Patch servers in order of reach. Our advice: domain controllers first, then any server that runs Exchange, then everything else. The November Windows updates cover the Search, Schannel, Kerberos and LDAP flaws above.

4. Tell staff what to watch for. Ask people not to open unexpected message files or Office attachments, even from a name they know, and to report them instead. If someone opened one before the update, our advice is to treat that password as exposed: reset it, sign the user out of all sessions, and review the account’s recent sign-ins and any new mail forwarding rules.

5. Block outbound SMB at the firewall. Microsoft’s guidance is to block TCP port 445 outbound to the internet at the corporate firewall, because few organizations need it. Microsoft also describes a setting that blocks NTLM for outgoing SMB connections on Windows 11 24H2 and Windows Server 2025. A caution: the advisory does not say which network protocol this flaw uses, so treat these as general protection against hash theft, not a confirmed fix for this bug.

6. Require signing where you can. Rapid7’s description of the relay attack points to SMB signing, LDAP signing and Extended Protection for Authentication as the safeguards that make a stolen hash less useful. Our advice: ask your IT provider whether they are turned on in your environment.

How we help

Knowing which Office build and which browser version each computer runs, and getting the fix onto all of them, is the job of remote monitoring and patching. Our service reports patch status continuously and confirms that updates actually installed, which matters when the question is whether every laptop has the November update.

Most attacks like this start with an email. Email security analyzes attachments and links before a message reaches a mailbox. Outbound rules, including the SMB block above, are part of firewall and routing work. If a password may have been exposed, incident response covers resetting credentials and checking what the account touched.

For law firms, municipalities and healthcare practices, one stolen login can reach confidential files and records. If you are not sure your computers have this month’s updates, contact us and we will help you find out.

We covered another KEV listing from the same day in Barracuda ESG Flaws Exploited: Patch the Gateway, and a different way attackers get past passwords in Device Code Phishing Beats MFA on Microsoft 365.

Sources

Trusted by dozens of businesses