All articles

NewsNovember 10, 20264 min read

Chrome, CVE-2026-125350: exploited use-after-free in XML

Google Chrome: CVE-2026-125350, a use-after-free in the XML component, is exploited and in the CISA KEV catalog. Affected versions and what to do right now.

A magnifying glass with a red warning sign on a blue digital background

On 10 November 2026 CISA, the US cybersecurity agency, added CVE-2026-125350, a use-after-free vulnerability in the XML component of Google Chrome, to its Known Exploited Vulnerabilities (KEV) catalog. On the same day CERT-FR, the response centre of the French agency ANSSI, published advisory CERTFR-2026-AVI-1488 on the Chrome updates of 9 November, which fix 16 vulnerabilities. According to CERT-FR, Google states that CVE-2026-125350 is actively exploited.

Technical details

According to the National Vulnerability Database (NVD) entry referenced by the KEV catalog, a use-after-free in the XML component of Google Chrome prior to 157.0.8103.50 allows a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page.

  • CVE: CVE-2026-125350, published on NVD on 10 November 2026, analysed and updated on 11 November.
  • Weakness: CWE-416 (Use After Free).
  • Chromium severity: high.
  • CVSS 3.1: 8.8, high severity, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: network attack, low complexity, no privileges required, but user interaction is needed (opening the malicious page); high impact on confidentiality, integrity and availability.
  • KEV catalog: added on 10 November 2026; for US federal agencies the remediation deadline is 24 November 2026. Use in ransomware campaigns is marked as “unknown”.
  • MITRE ATT&CK: the corresponding technique is T1203 (Exploitation for Client Execution).

The executed code stays inside the Chrome sandbox: the sources do not say whether the flaw was combined with other vulnerabilities in the attacks to escape it. The report in the Chromium issue tracker is restricted, and the available advisories do not describe the attack chain, list no indicators of compromise and do not say who is exploiting the flaw or against whom.

Affected versions

The CERT-FR advisory lists the following affected systems for the 9 November update as a whole:

  • Chrome for Windows and Linux prior to 157.0.8103.50;
  • Chrome for Mac prior to 157.0.8103.51;
  • Chrome Extended Stable for Windows and Mac prior to 156.0.8078.96.

The NVD entry for CVE-2026-125350 gives a single limit instead, Chrome prior to 157.0.8103.50, without distinguishing between operating systems and without mentioning the Extended Stable channel. The CERT-FR advisory does not specify which of the 16 vulnerabilities are fixed in the Extended Stable channel: for certainty, refer to the Google bulletin cited by CERT-FR, and bring every installation at least to the versions listed in any case.

Besides CVE-2026-125350, the CERT-FR advisory lists CVE-2026-121068, CVE-2026-121076, CVE-2026-121095, CVE-2026-121184, CVE-2026-121208, CVE-2026-121213, CVE-2026-121233 and CVE-2026-125342 through CVE-2026-125349. For these, CERT-FR reports that the risk is not specified by the vendor, and it marks only CVE-2026-125350 as exploited.

Impact for European and Italian companies

The browser is the tool people work with every day, on workstations and often on administration servers too. A flaw that can be exploited simply by opening a web page therefore concerns virtually every company. The user interaction required is minimal: visiting a compromised site or following a link received by email or chat is enough.

For entities in scope of NIS2, handling known vulnerabilities and updating software promptly are part of the required security measures. Inclusion in the KEV catalog is a useful signal for setting priorities, even though the catalog is binding only on US federal agencies. In healthcare, shared ward workstations and those connected to clinical systems should be included in the check: they are often among the last to be updated.

What to do right now

  1. Update Chrome at least to 157.0.8103.50 on Windows and Linux, to 157.0.8103.51 on Mac and to 156.0.8078.96 for the Extended Stable channel, following the vendor’s instructions, as CISA and CERT-FR request. If the fix cannot be applied, CISA advises discontinuing use of the product.
  2. Check that the update is actually applied: Chrome downloads new versions by itself but installs them when the browser is relaunched. Check the version at chrome://settings/help or in your inventory tool, including workstations that stay on for long periods, servers with the browser installed and off-site machines.
  3. Review enterprise policies: if updates are managed centrally or pinned to a version, unpin them or roll out the fixed release.
  4. Other Chromium-based browsers: the KEV catalog entry is titled “Google Chromium”, but the advisories cover Google Chrome. If your company uses other Chromium-based browsers, check their vendors’ advisories.
  5. Detection: with no public indicators, watch workstations for unusual processes started by the browser and anomalous outbound connections, and report suspicious events to your security team.

How ARXDOME helps

ARX Shield shows open vulnerabilities by machine and by package, with those already exploited by attackers highlighted: workstations running a vulnerable Chrome version stand out at once. ARX Horizon weighs vulnerabilities against the catalog of exploited ones, updated daily, so a flaw like CVE-2026-125350 rises to the top of the priorities. ARX Sentry collects logs and events from monitored machines, useful for looking for suspicious activity after a malicious page has been opened.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles