Home › Vulnerabilities

Google Chromium: Exploited Flaw CVE-2026-125350

Published November 10, 2026 · Last updated November 10, 2026

CVE KEV Use-After-Free Patch

What happened: On November 10, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-125350, a flaw in Google Chromium, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "Google Chromium Use-After-Free Vulnerability."

CISA's summary: "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."

CVE-2026-125350 is a use-after-free bug in the XML component of Google Chrome, and Google says an exploit for it is already circulating. Google fixed it in a Stable channel update dated Monday, November 9, 2026. On November 10, CISA added the flaw to its Known Exploited Vulnerabilities catalog, warning that it could affect other browsers built on Chromium, "including, but not limited to, Google Chrome, Microsoft Edge, and Opera."

What the bug does

A use-after-free happens when a program keeps using a piece of memory after it has handed that memory back. If an attacker can control what fills that memory next, they may be able to steer the program into running their own code. The weakness is catalogued as CWE-416.

The CVE record, published by Google's Chrome team, describes the impact: "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's own severity rating for the bug is High.

In practice, the record describes a victim loading a crafted web page. It does not describe any download, file opening or permission prompt as part of the attack.

What "inside the sandbox" means

Chrome runs web content in restricted processes, called the sandbox, which limit what code running there can reach. Code running inside the sandbox cannot normally read your files or install programs on its own. That is a real limit, but it is not a full defence. Attackers often pair a bug like this with a second flaw that escapes the sandbox. Neither Google nor CISA has said whether that happened here, and Google has not published details about the attacks.

Exploitation status

The release note says: "Google is aware that an exploit for CVE-2026-125350 exists in the wild." Google credits the report to an anonymous researcher and lists the report date as November 6, 2026, so the fix shipped within days. The bug tracker entry (issue 582442907) is restricted; Google notes that access to bug details "may be kept restricted until a majority of users are updated with a fix."

CISA's catalog entry gives U.S. federal civilian agencies until November 24, 2026 to apply the update, and lists ransomware use as "Unknown."

Affected and fixed versions

  • Affected: Google Chrome versions before 157.0.8103.50, according to the CVE record.
  • Fixed on Windows and Mac: 157.0.8103.50 or 157.0.8103.51.
  • Fixed on Linux: 157.0.8103.50.

Google says the update "will roll out over the coming days/weeks," so a browser may not have it yet even when automatic updates are on.

Other fixes in the same update

The same release fixes nine security bugs in total, so installing it closes more than the exploited flaw. Google rates seven as High and two as Medium:

  • CVE-2026-125346, another use-after-free in XML, reported by Arni Hardarson of Neonix Security.
  • CVE-2026-125344, a type confusion in V8, Chrome's JavaScript engine.
  • CVE-2026-125343, a buffer overflow in Compositing.
  • CVE-2026-125348, an out-of-bounds write in the GPU code.
  • CVE-2026-125347, incorrect authorization in FileSystem.
  • CVE-2026-125345, an uninitialized resource in WebGL.
  • CVE-2026-125349 and CVE-2026-125342, Medium-rated uninitialized resources in GPU code.

Google has said only that CVE-2026-125350 is being exploited. Google's release note credits Google itself with reporting six of the other eight.

Severity and who scored it

Google, the CVE Numbering Authority, did not publish a CVSS score in the CVE record; it gave only Chromium's "High" severity label. CISA's ADP later scored it CVSS 3.1 8.8 (High), vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, which NVD shows as a Secondary score. NVD has not published its own score. Its place in the CISA catalog, based on evidence of active exploitation, is the strongest signal of urgency here.

Other Chromium-based browsers

CISA's warning covers browsers that share Chromium code. Microsoft Edge, Opera, Brave, Vivaldi and others each ship their own builds on their own schedules. Microsoft's November 2026 security release, as fetched on November 10, did not yet list this CVE for Edge. Check each vendor's release notes rather than assuming a browser is patched because Chrome is.

What to do

  • Everyone using Chrome: update and relaunch now. Open the menu, go to Help, then About Google Chrome. Chrome checks for the update and downloads it. Click Relaunch. The fix does not take effect until the browser restarts, and tabs reopen afterward.
  • Check the version number. On the same About page, confirm you are on 157.0.8103.50 or later (or .51 on Windows and Mac).
  • IT administrators: push the update and force a restart. Use your browser management or software deployment tools to make sure managed devices reach 157.0.8103.50 or later, and set a relaunch deadline so users who never close their browsers still get the fix. CISA's November 24 deadline applies to U.S. federal agencies, and it is a sensible target for everyone else too.
  • Users of Edge, Opera, Brave and other Chromium browsers: watch for your vendor's update. Install it as soon as it is released, and relaunch the browser.
  • Security teams: plan for possible follow-on activity. Since Google has not shared attack details, keep endpoint protection current and look into unusual child processes started by the browser on systems that were behind on updates.

Sources: Google Chrome Releases blog, Stable Channel Update for Desktop (November 9, 2026); CVE record published by Google; CISA Known Exploited Vulnerabilities catalog.

What the National Vulnerability Database says

NVD first published CVE-2026-125350 on November 10, 2026. Its description, from the record's source ([email removed]), reads: "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)"

How serious is CVE-2026-125350?

The CVSS 3.1 base score is 8.8 out of 10 (High), scored by 134c704f-9b21-4f2e-91b3-4a467353bcc0. In plain terms: an attacker can reach the Chromium weakness over a network, including the internet; the attacker does not need an account; a user has to take an action, such as opening a file or link. The listed impact on Chromium data secrecy is high, on data integrity high, and on availability high. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Which Chromium versions are affected?

The CVE record lists these affected ranges:

  • 157.0.8103.50 up to, but not including, 157.0.8103.50

If your Chromium version falls in one of these ranges, check Google's advisory for the fixed release that applies to you.

What kind of weakness is it?

CISA and NVD map CVE-2026-125350 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):

  • CWE-416: Use After Free. MITRE's definition: "The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer."

CISA required action for CVE-2026-125350

CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "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."

Timeline for CVE-2026-125350

  • November 10, 2026: CISA adds CVE-2026-125350 to the KEV catalog.
  • November 10, 2026: NVD publishes CVE-2026-125350.
  • November 10, 2026: latest change to the NVD record (status: Analyzed).
  • November 24, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-125350.

Advisories and technical references

The NVD record for CVE-2026-125350 links to these references; tags in brackets are NVD's labels:

What to do

  • Run Google Chromium? Follow Google's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
  • Federal civilian agencies must act by November 24, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for Chromium too.
  • Ransomware use: CISA lists known ransomware campaign use for CVE-2026-125350 as "Unknown".
  • Don't run Chromium yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-125350" and asks for payment or remote access, that is a scam pattern, not a Google alert.

CVE-2026-125350 record details from CISA and NVD

  • CISA forensic triage flag for CVE-2026-125350: No
  • Attack complexity for CVE-2026-125350: low
  • CVE-2026-125350 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-125350: exploitability 2.8, impact 5.9.
  • Who mapped the weakness type: the address listed on google.com (Secondary)
  • NVD product identifiers (CPE): cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
  • References in the NVD record: 3 (1 tagged Release Notes, 1 tagged Vendor Advisory, 1 tagged Permissions Required).
  • CISA SSVC decision points for CVE-2026-125350 (from NVD): exploitation=active; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.