CVE-2026-125350
Google Chromium Use-After-Free Vulnerability
Description
CVE-2026-125350 is a use-after-free vulnerability in the XML component of Google Chrome prior to version 157.0.8103.50 that allows a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page. A victim only needs to visit a malicious or compromised website for the memory corruption to be triggered. Google rates the issue as High under the Chromium security severity scale, and the flaw affects Chromium-based browsers built on vulnerable versions. CISA has added CVE-2026-125350 to its Known Exploited Vulnerabilities (KEV) catalog, confirming that this Chrome zero-day-class vulnerability is being exploited in the wild.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| chrome | < 157.0.8103.50 |
References
- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html(Release Notes, Vendor Advisory)
- https://issues.chromium.org/issues/582442907(Permissions Required)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-125350(US Government Resource)
Weakness Type
CWE-416: Use After Free
A use-after-free occurs when software continues to use a pointer after the memory it references has been freed, so that reallocated memory can be read or written through the dangling pointer. In CVE-2026-125350, Chrome's XML handling keeps using an object after it has been freed, which an attacker can exploit with heap manipulation from a crafted page to gain code execution inside the renderer sandbox.
Learn more: CWE-416 — Use After Free
Impact Analysis
CVE-2026-125350 has a CVSS v3.1 base score of 8.8 (HIGH). The vulnerability is remotely exploitable without physical access, easy to exploit and needs no authentication, but requires user interaction in the form of visiting a crafted web page. Confidentiality, Integrity and Availability are all rated High: successful exploitation executes attacker code inside the Chrome sandbox, where it can access data processed by the renderer, such as page content and session information of the compromised tab, and serve as the first stage of a full browser compromise. Because browsers are present on virtually every workstation and CISA has confirmed exploitation, this Google Chrome vulnerability requires fast, organization-wide patching.
Exploit Maturity
CISA has confirmed active exploitation in the wild by adding CVE-2026-125350 to the KEV catalog on November 10, 2026; ransomware usage is not known. The EPSS score of 0.96% (62nd percentile) is moderate, which is typical for browser exploits used in targeted watering-hole or drive-by campaigns rather than in mass scanning. No public proof-of-concept is referenced; the Chromium issue is access-restricted. Because code execution is limited to the sandbox, attackers commonly combine such bugs with a separate sandbox escape to fully compromise the host.
Remediation
- Update Chrome now: Follow the KEV required action to "apply mitigations in accordance with vendor instructions" and update Google Chrome to version 157.0.8103.50 or later as announced in the Chrome stable channel update, before the CISA due date of November 24, 2026.
- Enforce the restart: Chrome applies updates only after a relaunch; use enterprise policies (for example a relaunch notification with a deadline) to make sure every browser actually runs the fixed version.
- Patch other Chromium-based browsers: Update Microsoft Edge, Brave, Opera, Vivaldi and embedded Chromium runtimes as soon as their vendors ship the corresponding Chromium fix.
- Monitor endpoints: Use EDR telemetry to look for unusual child processes of the browser, unexpected file writes and suspicious network connections after visits to unknown sites; block known malicious domains at the web proxy.
- Long-term hardening: Keep site isolation enabled, restrict browser extensions, and track Chrome version compliance centrally so that future use-after-free fixes are rolled out within days.
Technical Details
CVE-2026-125350 is a CWE-416 memory safety flaw in the XML processing code of Google Chrome. When a crafted HTML page drives the XML component into a state where an object is freed but a reference to it is still used, the attacker can reclaim the freed memory with controlled data through heap grooming and redirect execution flow, achieving arbitrary code execution inside the renderer sandbox. The CVSS v3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H reflects delivery over the network with low complexity and no privileges, conditioned on the user loading the malicious page, with high impact on all three security objectives within the unchanged scope of the sandboxed process.
Frequently Asked Questions
Is CVE-2026-125350 being actively exploited?
Yes. CISA added CVE-2026-125350 to the Known Exploited Vulnerabilities catalog on November 10, 2026, confirming exploitation in the wild. Ransomware usage is not known and the EPSS score is 0.96%.
What products are affected by CVE-2026-125350?
Google Chrome versions prior to 157.0.8103.50 are affected. Other Chromium-based browsers are affected until they integrate the corresponding Chromium fix.
How do I fix CVE-2026-125350?
Update Google Chrome to version 157.0.8103.50 or later and relaunch the browser so the update takes effect. Update other Chromium-based browsers as soon as their vendors release a fixed build.
How severe is CVE-2026-125350?
CVE-2026-125350 has a CVSS v3.1 score of 8.8 (HIGH) and is rated High by Chromium's own severity scale. A malicious web page is enough to execute code in the browser sandbox, and CISA has confirmed active exploitation.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.