CVE-2026-125350
Exploited in the wild. In CISA KEV since 2026‑11‑10. Fixed in 157.0.8103.50.
No public exploit knownFix157.0.8103.50Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.0.838493
What to do
Find your product and version, then upgrade to the build on the right.
- Google ChromeAffected: ≥ 157.0.8103.50, < 157.0.8103.50Upgrade to: 157.0.8103.50Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check your Chrome version via Settings > About Chrome
- If it's older than 157.0.8103.50, update it
- Restart the browser to apply the update
- Enable automatic updates so future fixes apply without manual action
Coverage timeline
0 publishersAdded to CISA KEV catalog
Sourced from public security reporting — each date is when it was published, not when it happened. 7 further articles named this CVE in wider roundups without reporting it as a distinct event.
What it is
From the CVE record
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)
In plain language
Written by AI from the recordA bug in Chrome's handling of certain web page content could let an attacker run harmful code if you visit a malicious page, but there's no sign anyone is actually exploiting it, and a fix is already out.
Use-after-free in Chromium's XML handling (CWE-416) allows a remote attacker to achieve code execution inside the sandbox via a crafted HTML page; no known exploitation or public PoC exists, fixed in 157.0.8103.50.
If you're affected
- Malware installation via browser
- Sandbox-contained code execution
- Operational disruption from compromised browser
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2026-11-10.
US federal agencies must remediate by 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.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.0% chance of exploitation activity in the next 30 days, which ranks it in the 62nd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained, driven by wide press coverage.
Lifecycle
11 events over 8 days, from the signal feeds we watch.
- OpenVAS check added
- Analysis publishedGoogle Patched Chrome's Eighth Zero-Day of 2026. The "Cooling Down" Story Lasted Six Days.patch available, record updated
- Added to CISA KEVpatch available, published, weakness classified, att&ck mapped, record updated, record updated
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored 8.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1190Exploit Public-Facing Applicationhigh confidence
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
References in the record
Analysis on the cve.tools blog
In the news
- 16th November – Threat Intelligence Report
- ⚡ Weekly Recap: N-able 0-Days, Windows 0-Days, Chrome 0-Days, Fridge 0-Days, and More Bad Days
- Never be afraid to ask questions
- Microsoft Fixes Nearly 1,100 Security Vulnerabilities – Krebs on Security
- Google patches eighth Chrome zero-day exploited in attacks this year
- Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026
- Chrome Update Patches Exploited XML Zero-Day, Eighth This Year
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Chrome, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI