ZeroDayAlert

CVE-2026-125350: Google Chromium Use-After-Free Vulnerability

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.

Google Chromium Added to KEV 2026-11-10 Federal due 2026-11-24 Known ransomware use

Required action — quoted from CISA

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). 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.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

Who is affected

This vulnerability affects multiple Chromium-based web browsers, including Google Chrome, Microsoft Edge, and Opera. The flaw exists in the XML component and can be triggered remotely through a specially crafted webpage. Any organisation or user running an affected browser version is potentially exposed if they visit a malicious or compromised website.

How to check whether this touches you

  • Inventory all endpoints and servers running Chrome, Edge, Opera, or any other Chromium-based browser; note the deployment context (kiosk, workstation, server, container).
  • Determine whether these browsers have internet access or are exposed to untrusted content (including email attachments and internal web applications).
  • Check the version number of each browser by navigating to the "About" menu or equivalent; version fingerprints alone do not confirm whether a patch has been backported, so cross-reference against your vendor's security advisories.
  • If you use enterprise management tools (such as Active Directory, Intune, or MDM platforms), query their deployment inventory for Chromium product versions and last-update timestamps.

What to do

  1. Review your internet exposure mapping under BOD 26-04 guidance: identify which browsers can reach the internet or process untrusted content, and prioritise those for immediate patching.
  2. Check the vendor security advisories from Google (Chrome), Microsoft (Edge), and Opera for the specific patched version number and apply updates via your standard patch management process; do not rely on auto-update alone.
  3. Until patching is complete, reduce exposure by disabling or restricting browser access on high-risk assets, particularly those handling sensitive data or exposed to external users.
  4. Enable logging of webpage visits and XML parsing errors (where available in your browser configuration or endpoint logging tools) to assist with retrospective investigation if needed.
  5. If you cannot patch within the federal remediation window (2026-11-24) and mitigations are unavailable, escalate to your risk and compliance teams for documented acceptance or discontinuation of the browser on that asset.

If you find you were exposed

Exploitation of use-after-free vulnerabilities typically occurs through social engineering or compromised websites, and may long predate public disclosure. Retrieve your web proxy logs, email gateway logs, and endpoint browser history for the period before the advisory date to identify visits to suspicious domains or downloads of potentially malicious files. Retain this evidence for forensic triage and retain logs for at least 90 days; if you identify suspicious activity, preserve the full session logs and notify your security incident response team.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-125350 is being exploited. It cannot tell you whether Chromium is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →