Google's Chrome 157 stable release fixes nine security bugs. On Nov. 10, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added one of them to its catalog of bugs attackers are already using, and Google's own release post says the same. CVE-2026-125350 is a use-after-free flaw in Chromium's XML handling. CISA added it to its Known Exploited Vulnerabilities (KEV) catalog the same day the CVE record was published, and gave federal civilian agencies until Nov. 24 to fix it.
Two independent signals point to active exploitation. Google's release post lists the bug with eight others and states that "Google is aware that an exploit for CVE-2026-125350 exists in the wild." CISA's KEV listing and the CISA assessment data attached to the NVD record mark exploitation as active. Google's post credits the bug report to an anonymous reporter, dated Nov. 6.
What is the bug?
The NVD entry, filed by Google's CVE team ([email protected]), describes CVE-2026-125350 as a "use after free in XML in Google Chrome prior to 157.0.8103.50." A use-after-free happens when a program releases a piece of memory but keeps a pointer to it and uses it later. If an attacker can control what fills that freed memory in the meantime, they can often make the program run code of their choosing. CISA's KEV entry lists the bug under CWE-416, the standard category for this class of flaw.
According to NVD, a remote attacker can "execute arbitrary code inside the sandbox via a crafted HTML page." In practice, the trigger is a web page. The victim only has to load attacker-controlled content, for example by clicking a link or visiting a compromised site. No login or prior access is needed.
The flaw is rated CVSS 3.1 8.8 (High), and Google's release post rates it High severity. Its vector breaks down as follows:
- Attack vector: Network. It can be exploited remotely over the web.
- Attack complexity: Low. No unusual conditions have to line up.
- Privileges required: None. The attacker needs no account or foothold.
- User interaction: Required. Someone has to open the malicious page.
"Inside the sandbox": why that is not as reassuring as it sounds
Chrome runs web content in sandboxed renderer processes. These processes are locked down so that code running in them cannot freely touch the file system or the rest of the operating system. The NVD description says code execution happens inside the sandbox, which is why the score stops at 8.8 rather than reaching the critical range.
Defenders should still treat it seriously. Code running in a renderer can read and tamper with whatever that process handles, which can include the content of the site being exploited. Browser attacks in the wild are also commonly built as chains, where a renderer bug like this one is paired with a separate sandbox escape. The sources do not say whether CVE-2026-125350 has been used in such a chain, and we are not suggesting it has. The point is simply that "sandboxed" describes the bug on its own, not the whole risk.
CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) data in the NVD record gives three judgments. Exploitation is active. The bug is not automatable, meaning it can't easily be turned into a self-spreading, hands-off attack, which fits the need for a user to visit a page. Its technical impact is total, CISA's way of saying an attacker who succeeds gets full control of the affected component.
Who is behind the exploitation?
The sources don't say. CISA's KEV entry, titled "Google Chromium Use-After-Free Vulnerability," marks known ransomware use as "Unknown" and names no threat actor or campaign. Neither NVD nor the Chrome release post attributes the activity to anyone. Until Google or another vendor publishes details, how the bug is being exploited and against whom remains unconfirmed.
Not just Chrome
The flaw sits in Chromium, the open-source engine underneath Chrome and many other browsers. CISA says it could affect multiple Chromium-based browsers, naming Chrome, Microsoft Edge and Opera. That list is "including, but not limited to," so other Chromium-based browsers, including ones users install themselves without telling IT, deserve a look too.
The sources we checked give fixed version numbers only for Google Chrome. Teams running Edge, Opera or other Chromium browsers will need to check each vendor's own release notes to confirm the Chromium fix has been picked up.
The rest of Chrome 157's fixes
The stable channel update moves Chrome to 157.0.8103.50/.51 for Windows and Mac, and 157.0.8103.50 for Linux, rolling out over the coming days and weeks. Besides CVE-2026-125350, Google lists six other High-severity issues (CVE-2026-125343, -125344, -125345, -125346, -125347 and -125348) and two rated Medium (CVE-2026-125342 and -125349). One of the other High bugs, CVE-2026-125346, is also a use-after-free in XML, but Google's post flags only CVE-2026-125350 as having an exploit in the wild, and only CVE-2026-125350 is on CISA's KEV list. The release is still worth installing quickly for the other High-rated fixes alone.
What It Means for Defenders
Who is affected: anyone running Google Chrome older than 157.0.8103.50, plus users of other Chromium-based browsers, including Edge and Opera per CISA, until their vendors ship the fix.
What to do now:
- Update Chrome to 157.0.8103.50 (or .51 on Windows and Mac). Chrome downloads updates on its own, but the fix doesn't take effect until the browser restarts. Users who leave their browser open for weeks stay exposed. If you manage Chrome centrally, force a relaunch or set a short relaunch deadline. Because the rollout is staged over days or weeks, use the manual update check if the fix has not arrived yet.
- Check your fleet, not just your own machine. Use your endpoint management or inventory tools to find any Chrome install still below 157.0.8103.50. Watch for unmanaged copies and portable installs.
- Track Edge, Opera and other Chromium browsers separately. Watch for each vendor's update that includes this Chromium fix and push it once it's out. Our sources do not give their fixed version numbers.
- Federal civilian agencies: CISA's KEV entry sets a Nov. 24, 2026 remediation deadline and cites Binding Operational Directive 26-04 in its required action. Agencies that can't patch by then should follow the mitigation-or-discontinue guidance in the KEV entry.
- Contractors and CMMC shops: BOD deadlines don't legally bind private companies. Still, KEV is a widely used shortlist for what to patch first, and a known-exploited browser bug on machines that handle Controlled Unclassified Information is exactly what an assessor will ask about. Record the update in your vulnerability management log.
- Small businesses: the most useful single step is making sure every staff browser is actually restarted onto the new version. Spot-check a few machines on Chrome's "About" page.
The sources describe no workaround or configuration change that blocks this flaw. Updating is the fix. Because the attack needs someone to open a malicious page, the usual web-filtering and phishing defenses help reduce exposure while patches roll out. They don't replace the update.