CVE-2026-125350
CVE-2026-125350 is a security flaw in Chrome and other Chromium browsers, the open-source browser that Chrome, Edge, Brave and Opera are built on. A booby-trapped web page can run an attacker's code through Chrome and other Chromium browsers. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 10 Nov 2026.[1]
Chrome and other Chromium browsers is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Fixed in version 157.0.8103.50 of Chrome.
Description
CISA calls it an use-after-free in Google Chromium. In its words: “Google Chromium contains a use-after-free vulnerability in the XML component that could allow a remote attacker to execute arbitrary code inside the sandbox via a specially crafted webpage. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.”[1]
The underlying weakness is use after free (CWE-416), in MITRE’s list of common software weaknesses.[2]
It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record lists one fixed version: everything before it is affected.[2]
| Product | Fixed in |
|---|---|
| Chrome | 157.0.8103.50 |
Every device with Chrome and other Chromium browsers needs the update.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 10 Nov 2026, within a day of it being made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 24 Nov 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at under 1%. That’s in the top 38% of the flaws it scores.[4]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
Google has published a fix or advice.[3] CISA’s required action: “Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes).”[1]
- Update Chrome and other Chromium browsers now.Chrome updates itself, but only finishes when you restart it: open the menu, choose Help, then About Google Chrome, and click Relaunch. Edge, Brave, Opera and Vivaldi need the same. Then turn on automatic updates, so the next fix arrives on its own.
- Check you’re on 157.0.8103.50 or later.Fixed in version 157.0.8103.50 of Chrome. Anything older is what attackers are going after.
- If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.
Fixed in Chrome 157.0.8103.50, Brave 1.99.56 and Microsoft Edge 156.0.4314.80. Each says whether to update now and how.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at under 1%.[4] | |
| CISA’s deadline for US government agencies to fix it.[1] |
See also
In the news
- Chrome needed three security updates in nine days · Situation Room,
- November's Microsoft update fixes an Outlook flaw already used in attacks · Situation Room,
Other Chrome and other Chromium browsers flaws
- CVE-2026-2441: CSS use-after-free ·
- CVE-2025-14174: out of bounds memory access ·
- CVE-2025-6558: ANGLE and GPU improper input validation ·
- CVE-2024-4671: visuals use-after-free ·
- CVE-2021-37976: information disclosure ·
- CVE-2021-21166: race condition ·
Other Google flaws
- CVE-2026-111497, Google Brotli: unchecked return value ·
- CVE-2026-58704, Google Pixel: improper authorization ·
- CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
- CVE-2026-85046, Chrome and other Chromium browsers: type confusion ·
- CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·
Other use after free flaws
- CVE-2026-109619, PHP: stale internal request-state ·
- CVE-2026-109618, PHP: memory corruption ·
- CVE-2026-68820, Microsoft Windows Ancillary Function Driver for WinSock: use-after-free ·
- CVE-2010-0249, Microsoft Internet Explorer: use-after-free ·
- CVE-2020-9715, Adobe Acrobat: use-after-free ·
Added the same day
- CVE-2026-20320, Cisco BroadWorks: improper restriction of XML external entity reference ·
- CVE-2026-124194, Microsoft Office: outlook missing user interaction for potentially unsafe action ·
- CVE-2026-116606, Barracuda Networks Barracuda Email Security Gateway (ESG): email security gateway (ESG) authentication bypass using an alternate path or channel ·
- CVE-2026-111793, Openwave Messaging Limited Webtop Media Transcoder: incorrect resource transfer between spheres ·
- CVE-2026-111560, Barracuda Networks products: OS command injection ·
Every Google flaw on CISA’s list · Everything added in November 2026
References
- ^ Cybersecurity and Infrastructure Security Agency. “Google Chromium Use-After-Free Vulnerability”. Known Exploited Vulnerabilities Catalog, added 10 Nov 2026.
- ^ National Institute of Standards and Technology. “CVE-2026-125350 Detail”. National Vulnerability Database, published 10 Nov 2026.
- ^ Google. Advisories and fixes: chromereleases.googleblog.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.010, percentile 62.4, 19 Nov 2026.
- CVE Program. “CVE-2026-125350”. The official CVE record.
This article is built from CISA’s catalog (version 2026.11.18), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.

