Google rates it High and says an exploit exists in the wild. NVD describes code execution inside the browser sandbox after a victim opens a crafted HTML page.A use-after-free means software accesses memory after releasing it. In this case, the public records identify the component and outcome, but do not describe the exact faulty operation. Teams can track remediation through a vulnerability intelligence platform.
What it allows
How Does the CVE-2026-125350 XML Flaw Work?
Google identifies a use-after-free in Chrome's XML component. NVD says a remote attacker can use a crafted HTML page to execute arbitrary code inside the sandbox. The public descriptions do not establish an escape from that sandbox.
The attack chain therefore starts with a user opening attacker-controlled web content. The vulnerable XML processing path can then reach freed memory and permit code execution in the browser sandbox. This is our reading of the two public descriptions; the precise trigger is restricted.
What Is Known About Exploitation?
Google's November 9 release says an exploit for this CVE exists in the wild. CISA added it to the KEV catalog on November 10, with a November 24 remediation due date for covered federal agencies. Neither statement attributes a campaign or identifies a victim.
Brandefense Blackhole counted 18 dark chat posts mentioning CVE-2026-125350 from August 16 through November 14, 2026. The unit is posts mentioning the CVE, not incidents or distinct actors. A separate GitHub search found four public repositories named for this CVE as of November 14; repository names do not verify exploitability.
For the dated release and operational response, see our Chrome CVE-2026-125350 exploitation alert. This profile explains the flaw, affected builds, and version checks.
Who is affected
Which Chrome Builds Need the CVE-2026-125350 Fix?
NVD lists Google Chrome versions before 157.0.8103.50 as affected. Google's November 9 desktop release names 157.0.8103.50 and .51 for Windows and Mac, and 157.0.8103.50 for Linux. Check the installed browser build after updating because rollout can take time.
CISA says other Chromium-based browsers may also be affected, including Microsoft Edge and Opera. That is a potential exposure statement, not a verified fixed-version list for those products. Check each browser vendor's own advisory and installed build before marking it remediated.
Record the browser and operating system in your patch management inventory. Include managed desktops and alternate Chromium-based browsers so the version check covers the browsers users actually run.
Timeline
- 2026-11-09
Google released Chrome desktop 157.0.8103.50/.51 for Windows and Mac, and 157.0.8103.50 for Linux. Its notice said an exploit for CVE-2026-125350 exists in the wild.
- 2026-11-10
CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog.
What to do
-
Inventory installed browsers
Identify Chrome installations by operating system and installed version. Include other Chromium-based browsers for separate vendor-advisory checks.
-
Update Chrome desktop
Apply Google's November 9 stable update. Its release lists 157.0.8103.50/.51 for Windows and Mac, and 157.0.8103.50 for Linux.
-
Verify the running build
Restart the browser if required, then read its About or management-reported version. Confirm Chrome reports a fixed release for its platform; do not assume an update download completed installation.
-
Check other Chromium browser advisories
CISA warns that other Chromium-based browsers may be affected. Confirm each vendor's affected versions and fixed build before closing those assets.
-
Review suspected activity
Prioritize investigation where an affected browser opened untrusted content. Preserve browser and endpoint telemetry, and assess any suspicious child processes or unusual browser behavior.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-125350 in Brandefense Atlas
The Atlas record of CVE-2026-125350: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-125350?
It is a use-after-free in Chrome's XML component. NVD says a crafted HTML page can lead to arbitrary code execution inside the browser sandbox.
Which Chrome version fixes CVE-2026-125350?
Google's desktop release lists 157.0.8103.50/.51 for Windows and Mac, and 157.0.8103.50 for Linux. Verify the installed build after updating.
Is CVE-2026-125350 in CISA KEV?
Yes. CISA added it on November 10, 2026. Its catalog lists November 24 as the remediation due date for covered federal agencies.
Does the Chrome fix also specify versions for Edge or Opera?
No. CISA says other Chromium-based browsers may be affected. Check each browser vendor's advisory for its own affected and fixed builds.
Sources
- Stable Channel Update for Desktop, November 9, 2026Google Chrome Releases
- CVE-2026-125350 DetailNIST NVD
- Known Exploited Vulnerabilities CatalogCISA