~/f4n6 $ grep -r "Chromium XML use-after-free CVE-2026-125350 added to CISA KEV" ./investigations/ --include="*.md"

Chromium XML use-after-free CVE-2026-125350 added to CISA KEV

Jeff Davies 10 Nov 2026 6 min read

1. Executive summary

CVE-2026-125350 is a use-after-free in the XML component of Google Chromium, scored CVSS 8.8 HIGH (CWE-416) in NVD, and it was added to CISA KEV on 2026-11-10. Google says an exploit exists in the wild, and the fix shipped in Chrome 157.0.8103.50/.51 for Windows and macOS and 157.0.8103.50 for Linux, with an Android build at 157.0.8103.50. The flaw affects every Chromium-based browser, so Chrome, Edge and Opera estates are exposed until the vendor build is applied. For EMEA financial services the risk is concentrated in browser fleets on staff endpoints and in any customer-facing web property that renders untrusted XML; there is no evidence in public reporting tying this CVE to a financial-sector victim, and Google has named no actor or target.

2. Regulatory framing

Article Trigger (the fact in this item) Practical impact
DORA Art. 17 An actively exploited code-execution flaw in a browser component that is part of the ICT estate requires the incident management process to cover detection, response and the patch decision. The patch rollout and any exploitation finding must run through the documented ICT incident process, with records of the decision and its timing.
DORA Art. 18 Exploitation state is confirmed by Google and by CISA KEV listing, which is the classification input for whether an event is an ICT-related incident. Clients must classify any observed exploitation against the Art. 18 criteria rather than treating a browser patch as routine maintenance.
NIS2 Art. 21(2)(d) The exposure sits in a third-party browser component supplied by Google and redistributed through Microsoft and Opera, so supply chain security measures apply to how those updates are received and verified. Update intake from each browser vendor must be tracked and evidenced as a supply chain control.

3. Technical analysis & attack chain

The confirmed sequence, from Google's advisory as reported and from the CISA KEV entry:

  1. A remote attacker delivers a crafted webpage to a victim running an affected Chromium build.
  2. The page drives the XML component into a use-after-free: the component keeps a pointer to memory after it has been freed (CWE-416).
  3. The resulting memory corruption allows arbitrary code execution inside the browser sandbox.

Google's wording is that it "is aware that an exploit for CVE-2026-125350 exists in the wild." That is the full extent of the vendor statement. Google has not disclosed the delivery method, the targets, the identity of the attackers, or what the exploit does once it runs. The vulnerability was reported anonymously on November 6, according to The Register; Malwarebytes describes the reporter as an unnamed third party notified on the same date. Google is withholding further technical detail until enough users have installed the fix, its standard practice for exploited bugs.

The affected surface is the XML component, the parser Chrome uses for structured XML content. The flaw is reachable through a webpage, which is why the impact extends across Chromium-derived browsers: Google Chrome, Microsoft Edge and Opera are named in the CISA entry. Fixed builds are Chrome 157.0.8103.50/.51 for Windows and macOS and 157.0.8103.50 for Linux; Chrome 157.0.8103.50 for Android carries the same security fixes unless otherwise noted. ANSSI CERT-FR lists the affected versions as Chrome earlier than 157.0.8103.50 on Linux, earlier than 157.0.8103.50 on Windows, earlier than 157.0.8103.51 on Mac, and Chrome Extended Stable earlier than 156.0.8078.96 on Windows and Mac.

The same update carries eight other fixes, including high-severity flaws in WebGL, FileSystem, GPU, Compositing and the V8 JavaScript engine, and a second XML use-after-free, CVE-2026-125346, reported by Arni Hardarson of Neonix Security in October. Google has not indicated that CVE-2026-125346 is exploited. Those CVEs have no entry in the verified data used for this note, so no score or exploitation state is asserted for them here.

Confidence caveats. The exploitation claim rests on Google's own statement, repeated by The Register, The Hacker News, Malwarebytes and ANSSI; it is corroborated across those outlets but originates from a single vendor. No source gives an initial access vector beyond "crafted webpage", no source gives post-exploitation behaviour, and no source attributes the activity to a named actor. HKCERT, per Malwarebytes, rates the overall risk of the update "Extremely High" and notes that some flaws in it could allow denial of service, security restriction bypass and remote code execution; that rating covers the whole update, not CVE-2026-125350 alone. The Hacker News records the CVSS as N/A, which conflicts with the NVD score of 8.8 HIGH used throughout this advisory.

4. Mitigation & containment

P1 (within 24 hours)

  • Update Chrome to 157.0.8103.50 or 157.0.8103.51 on Windows and macOS, and 157.0.8103.50 on Linux. On Android, update through Google Play to 157.0.8103.50. For fleets on Chrome Extended Stable, the fixed build is 156.0.8078.96 on Windows and Mac.
  • Force the update rather than waiting for the staged rollout: open About Google Chrome from the Settings or Help menu, let it check and download, then click Relaunch when prompted. A browser that is never closed, or an extension that blocks the update, can leave a host behind.
  • Confirm the running version on a sample of endpoints after relaunch. A relaunch that did not take leaves the old build in memory.
  • Apply the equivalent vendor update for Microsoft Edge and Opera, which share the Chromium component. No fixed Edge or Opera build number is given in public reporting for this CVE, so track each vendor's own release channel.
  • Treat this as the KEV remediation item it is: CISA's required action is to apply mitigations per vendor instructions, with a due date of 2026-11-24.

P2 (within 72 hours)

  • Inventory browser builds across the estate, including non-managed installs and virtual desktop images, and record which hosts are still below the fixed versions.
  • Where a host cannot be updated immediately, restrict its use for browsing untrusted content and raise logging on it.

P3 (within 7 days)

  • Add browser version to the standard endpoint compliance check so the next Chromium zero-day is caught by the same control.
  • Review whether any customer-facing service parses untrusted XML with an embedded Chromium engine, and confirm the engine build against the fixed versions above.

No workaround short of the vendor update is named in public reporting. No exploitation indicators are published, so containment by indicator is not possible; containment rests on version.

5. Indicators of compromise

No indicators of compromise available in the source material. No file hashes, domains, IP addresses, file paths or command lines are published for CVE-2026-125350. Google has withheld technical detail, and no source names an exploit sample.

Behavioural indicators

behaviour where to observe confidence
Chromium-based browser rendering a crafted webpage and crashing or corrupting memory in the XML component Endpoint crash telemetry and browser crash reports for Chrome, Edge and Opera Low; inferred from the CWE-416 mechanism, not from a published observation
Browser process executing code that did not originate from a normal navigation EDR process and child-process telemetry on browser binaries Low; no post-exploitation behaviour is published

6. Detection

Insufficient indicators to author detection rules. The sources give no strings, paths, mutexes, command lines or network artefacts belonging to the exploit, and a rule keyed on the CVE identifier or product name would detect reporting about the flaw rather than the flaw itself. Detection for now rests on version compliance: alert on any Chromium-based browser below 157.0.8103.50/.51 (or Extended Stable below 156.0.8078.96 on Windows and Mac) reporting to the estate.

CVE assessment

1 referenced CVE — 1 actively exploited (CISA KEV)

CVE CVSS Exploited EPSS Summary
CVE-2026-125350 8.8 High ⚠ KEV 2026-11-10 — Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sa…

7. Sources

  • NVD, CVE-2026-125350 detail, https://nvd.nist.gov/vuln/detail/CVE-2026-125350, published 2026-11-10
  • CISA Known Exploited Vulnerabilities, CVE-2026-125350 entry, https://nvd.nist.gov/vuln/detail/CVE-2026-125350, KEV added 2026-11-10
  • The Register, "Chrome zero-day whack-a-mole continues as 2026 tally hits 8", https://www.theregister.com/security/2026/11/10/chrome-zero-day-whack-a-mole-continues-as-2026-tally-hits-8/5308732, 2026-11-10
  • The Hacker News, "Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026", https://thehackernews.com/2026/11/google-issues-chrome-security-update.html
  • Malwarebytes Labs, "Update Chrome now to fix a flaw attackers are exploiting", https://www.malwarebytes.com/blog/bugs/2026/11/update-chrome-now-to-fix-a-flaw-attackers-are-exploiting
  • ANSSI CERT-FR, "Multiples vulnérabilités dans Google Chrome", https://www.cert.cyber.gouv.fr/avis/CERTFR-2026-AVI-1488/, 2026-11-10
  • Google Chrome Releases, Stable Channel Update for Desktop, https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html, 2026-11-09
  • Google Chrome Releases, Extended Stable Update for Desktop, https://chromereleases.googleblog.com/2026/11/extended-stable-update-for-desktop_0910980127.html, 2026-11-09

8. Adverse Trace position

Adverse Trace assesses CVE-2026-125350 as CVSS 8.8 HIGH with confirmed in-the-wild exploitation and a CISA KEV listing dated 2026-11-10; the exploitation claim is Google's and is repeated by four outlets, but no actor, target set or post-exploitation behaviour is public, so attribution is unconfirmed and no campaign link is asserted. For EMEA financial services the practical exposure is the browser fleet and any Chromium-embedded component that parses untrusted XML; a single unpatched endpoint is a code-execution path inside the sandbox, and the KEV due date of 2026-11-24 sets the outer bound for remediation. We will track vendor build numbers for Edge and Opera, watch for the technical detail Google has said it will release once adoption is sufficient, and reissue this note if an actor or exploitation pattern is named. Clients should confirm their Chrome build against 157.0.8103.50/.51 and report the result to us so we can size the residual exposure across the sector.


Read the original source →

Published via PulseTrace — Adverse Trace threat intelligence.

Post this to LinkedIn
Formatting is converted automatically — headings, bullets, a link back & hashtags. Paste straight in.
J
Jeff Davies