CVE-2026-125350 · Published 10 Nov 2026
Google Chromium
On CISA's KEV list the day it was disclosed; 6 public exploits.
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.
CISA required action (federal due date 24 Nov 2026): 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.
Signals
- KEV, exploited in the wild
- yes, added 10 Nov 2026, due 24 Nov 2026
- EPSS, 30-day forecast
- 1.0%, 62th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 10 Nov 2026 to today
- KEV
- First PoCsame day
- Disclosedsame day
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 5 dispatches
- Google patches eighth Chrome 0-day of 2026 · KEV
- N-able releases emergency fixes for 33 vulnerabilities in N-central RMM platform · KEV
- Hronaut 3.14.27 is out with Chromium 156.0.8078.96 (Electron 45.3.0). It fixes CVE-2026-125350, a use-after-free in XML that Google says is exploited in the wild, plus 10 other · KEV
- Critical 0-day vulnerability exploited in Google Chrome browser · KEV
- Critical 0-day vulnerability exploited in Google Chrome browser · KEV
Public exploit code 6 known · links only
GitHub PoCs 6Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars6
- Frostmoon39206/CVE-2026-125350-PoCTrust ok 1005 stars
Technical analysis and skeleton PoC for CVE-2026-125350 (Chrome XML UAF)
created 10 Nov 2026
- TJT001/CVE-2026-125350-PoCTrust ok 1001 stars
Google Chrome XSLT pattern-cache Use-After-Free (CVE-2026-125350) crash PoC — affected < 157.0.8103.50
created 11 Nov 2026
- al4n4n/CVE-2026-125350Trust ok 1000 stars
Moved to al4n4n/achilles-heel: https://github.com/al4n4n/achilles-heel/tree/main/CVE-2026-125350
created 13 Nov 2026
- ashrafzaryouh/CVE-2026-125350Trust ok 1000 stars
CVE-2026-125350
created 10 Nov 2026
- dexteon/cve-2026-125350-pocTrust ok 1000 stars
Research notes for cve-2026-125350-poc
created 12 Nov 2026
- LLCForge/CVE-2026-1253500 stars
Caution 75 · 1 flag
- new owner account (new_owner_account)
PoC for CVE-2026-125350 — Google Chrome XML use-after-free in renderer (CVSS 8.8, Chrome < 157.0.8103.50, KEV)
created 18 Nov 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.