Advisory

CVE-2026-125350: Google Chromium Use-After-Free Vulnerability — what to do now

CVE-2026-125350 affects Google Chromium and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog — it is being exploited in the wild, rated HIGH (CVSS 8.8). Here is what it is, who is affected, and the response. No exploit details.

TL;DR: CVE-2026-125350 is a known-exploited vulnerability in Google Chromium. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Then confirm no exposed, unpatched instance remains on your perimeter.

What CVE-2026-125350 is

According to the public vulnerability record, Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

CISA summarises it as: 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.

Affected product & severity

CVE-2026-125350 affects Google Chromium. Confirm exact affected and fixed versions against the vendor's advisory.

PropertyDetail
CVECVE-2026-125350
VendorGoogle
ProductChromium
CVSS8.8 (HIGH)
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
WeaknessCWE-416
Added to CISA KEV2026-11-10

Why it is urgent

This CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-11-10) — a list of flaws with confirmed exploitation in the wild. US federal agencies are required to remediate KEV entries on a deadline; for everyone else it is a strong signal to prioritise this now rather than wait. There is no proof-of-concept or exploit detail in this advisory by design.

What to do now

  1. Follow 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 guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  2. Apply the vendor's patch or mitigation for Google Chromium on every affected instance, per the official advisory linked below.
  3. Inventory every instance — production, staging, legacy and third-party appliances that bundle it. You cannot patch what you have forgotten you run.
  4. Verify the version actually deployed, not the one you think you run; the risk is the build actually serving traffic.
  5. Check for internet exposure. A known-exploited flaw on a reachable instance is an active risk — confirm none is exposed that should not be.

How to confirm your exposure

The hard part of a known-exploited CVE is rarely the patch — it is knowing where a reachable, unpatched instance still exists: a forgotten host, a staging box that drifted public, a third-party appliance. AssurePort's network and host penetration testing discovers exposed services, fingerprints their versions, and correlates them against known-exploited vulnerabilities — so a newly-weaponised CVE is checked against your real external footprint, including the hosts you don't have on a list. An on-demand scan after you patch shows whether the fix is in place on your own systems; it is a point-in-time check that you start, not an ongoing watch.

Sources & further reading: NVD CVE-2026-125350 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: chromereleases.googleblog.com, issues.chromium.org, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

What is CVE-2026-125350?

CVE-2026-125350 is a vulnerability in Google Chromium, rated HIGH (CVSS 8.8), listed in the CISA Known Exploited Vulnerabilities catalog. Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

Is CVE-2026-125350 being exploited?

Yes — it is in the CISA KEV catalog (added 2026-11-10), which lists vulnerabilities with confirmed in-the-wild exploitation. Treat it as an active, prioritise-now risk.

Which products are affected?

Google Chromium. Confirm the exact affected and fixed versions against the vendor's official security advisory before acting.

What should I do right now?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Then inventory every instance, verify the version actually deployed, and confirm none is exposed and unpatched on your perimeter.