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…
- Exploited
- Yes, on CISA KEV
- Fix
- Fixed in 157.0.8103.50
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 157.0.8103.50.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Added to CISA KEV Nov 10; federal deadline Nov 24. Scores 92 on the cve.now Index; published Nov 10
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 92/100 · #6 in the past year · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: active
- Automatable: no
- Technical impact: total
Summary
Google Chrome is affected by a use-after-free bug in its XML handling. A remote attacker could run arbitrary code inside the browser sandbox by luring a victim to a crafted HTML page.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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)
cve.now Index
- Exploitation40/40Listed in CISA's Known Exploited Vulnerabilities catalog
- Exposure22/25Actively exploited, reachable over the network without a login
- Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
Impact
- Widely used
“Statcounter puts Chrome at 66.98 percent of desktop browser share worldwide in October 2026.”Source: blog.ostorlab.co
What to do
Upgrade to a fixed version: 157.0.8103.50.
Fix it by , CISA's deadline for US federal agencies.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125350 (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…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125350 (entry last updated 2026-11-10): Affected: - Google Chrome: from 157.0.8103.50, fixed in 157.0.8103.50 Fixed versions: 157.0.8103.50. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-125350 is listed as known exploited (added 2026-11-10, remediation due 2026-11-24). This KEV status is for CVE-2026-125350 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html - https://issues.chromium.org/issues/582442907 - https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-125350 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125350 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125350.
Timeline
- cve.now early warning
Google patches Chrome XML zero-day reported as exploited in attacks
1 day - Added to CISA KEV
CISA has evidence of exploitation in the wild
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: active · Automatable: no · Technical impact: total
- Record last updated14 days
- CISA remediation deadline
Due date for US federal agencies to patch
Affected versions
- Google Chrome
From 157.0.8103.50 · fixed in 157.0.8103.50
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
CISA KEV · 2
Establishes: Exploitation in the wild, for this CVE only.
- Listing
- Link
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125350
Is CVE-2026-125350 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-11-10, which means it has evidence of attacks. US federal agencies must fix it by 2026-11-24. No public exploit code is tracked.Source: cisa.gov, cve.now feed data
Which versions are affected by CVE-2026-125350?
Chrome: from 157.0.8103.50 before 157.0.8103.50.Source: cve.now feed data
How do I fix CVE-2026-125350?
Upgrade to a fixed version: 157.0.8103.50.Source: cve.now feed data