CVE-2026-125350highunder attackCWE-416

CVE-2026-125350: high-severity vulnerability in Google Chrome

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

71Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA and has a public proof of concept.

ssvc Actcvss 8.8epss 1.0%
from disclosure to weaponsame day
Published on NVDNov 10
1st PoCNov 10
CISA KEVNov 10
Action required by CISAfederal deadline: 2026-11-24

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.

In short

A memory bug in Google Chrome's XML handling can be triggered by a malicious web page, potentially letting an attacker run code inside the browser's sandbox. Updating Chrome to version 157.0.8103.50 or later fixes it.

Technical detail

Use-after-free (CWE-416) in the XML component of Google Chrome before 157.0.8103.50, reachable remotely via a crafted HTML page (CVSS 8.8, High). Successful exploitation allows arbitrary code execution inside the renderer sandbox, requiring the victim to visit an attacker-controlled page; no sandbox escape is described in the advisory.

Summary generated and translated by AI from the official description.
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)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
Google · Chrome
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.