Skip to content
Blog

Google · Google Chrome · Chromium

Google Chrome 157.0.8103.50: CVE-2026-125350, Exploited Use-After-Free in XML Added to KEV

CVE-2026-125350, a use-after-free in Chrome's XML component, is exploited and now in CISA KEV. Chrome 157.0.8103.50 fixes it. Versions, detection, patching.

3 min readCVE-2026-125350

On November 10, 2026, NVD published CVE-2026-125350, a use-after-free in Google Chrome's XML component, fixed in Chrome 157.0.8103.50. The same day, CISA added it to the Known Exploited Vulnerabilities catalog: it is being exploited.

That changes the picture compared with Chrome 156 in late October, whose CVEs were not exploited. This update is no longer routine, it is urgent.

ItemValue
CVECVE-2026-125350
ComponentXML
WeaknessUse-after-free (CWE-416)
CVSS 3.1 (Chrome CNA)8.8 HIGH
VectorAV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Chromium severityHigh
NVD statusAnalyzed
Added to KEV2026-11-10
CISA due date2026-11-24

The score is the one published by the Chrome CNA (Google); NVD has not added its own.


What the description says

Per NVD, a use-after-free in XML handling in Chrome before 157.0.8103.50 let a remote attacker execute arbitrary code inside the sandbox through a crafted HTML page.

Two details matter:

  • "Inside the sandbox": the code runs in the renderer process, isolated from the operating system. Taking over the machine usually requires a second bug that escapes the sandbox. Nothing in the public data says which one, if any, was used; that is simply the usual shape of browser exploitation, not information about this particular exploit.
  • UI:R: the user has to visit the malicious page. A link in an email, a malicious ad or a compromised site is enough.

As usual with Chromium, the bug report stays restricted until most browsers have updated. CISA notes the flaw can affect other Chromium-based browsers, including Microsoft Edge and Opera. Ransomware use is listed as "Unknown".


Affected versions

NVD ties the CVE to Google Chrome before 157.0.8103.50 (excluded bound in the CPE configuration). 157.0.8103.50 is therefore the first fixed version, and anything later is fixed too.

NVD does not list other Chromium browsers (Edge, Brave, Opera, Vivaldi and others). They ship the fix on their own schedule, so check each vendor's advisory.


Detection

  • Deployed version: chrome://version on a single machine, or your console inventory (Chrome Browser Cloud Management, Intune, Jamf, Group Policy) to find anything below 157.0.8103.50.
  • Browsers that never restart: Chrome stages updates in the background and only applies them on relaunch. A machine left on for days may still run the old build.
  • Other Chromium browsers: inventory Edge and the rest separately, including apps that embed Chromium.

Mitigation

  1. Roll out Chrome 157.0.8103.50 or later everywhere, without waiting for your usual cycle.
  2. Force a relaunch with the RelaunchNotification and RelaunchNotificationPeriod policies.
  3. Track Edge and other Chromium browsers and apply their fix as soon as it ships.
  4. Check again two days later: the share of machines actually running 157 is the only metric that counts.

Why continuous monitoring of your browsers matters

An exploited browser CVE lands without warning, and the gap between disclosure and attacks is measured in days. Knowing which version runs on each machine lets you measure real exposure instead of assuming auto-update did its job.

With cveo.tech, register your browsers with their versions and get an alert as soon as a critical CVE or KEV listing affects them.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.