~/f4n6 $ grep -r "Chrome zero-day CVE-2026-125350 exploited in wild" ./investigations/ --include="*.md"

Chrome zero-day CVE-2026-125350 exploited in wild

Jeff Davies 10 Nov 2026 5 min read

1. Executive summary

Google issued a Chrome Stable channel update on November 9, 2026, bringing desktop to 157.0.8103.50/.51 on Windows and Mac and 157.0.8103.50 on Linux, and Android to 157.0.8103.50. The release fixes nine vulnerabilities, one of which, CVE-2026-125350, is a use-after-free in Chrome's XML component that Google says is exploited in the wild. CVE-2026-125350 has no NVD entry: no CVSS score, EPSS value or CISA KEV state is recorded against it, so the high-severity rating in this advisory is Google's own, not a verified score. Google has not named the attackers, the targets, the delivery method or the exploit's effect, and HKCERT rates the overall risk of the update as "Extremely High". For EMEA financial services the exposure is the browser on every managed desktop and any unmanaged device reaching web banking or internal web applications; the fix is available now and the risk is concentrated in endpoints that have not yet taken it.

2. Regulatory framing

Article Trigger (the fact in this item) Practical impact
DORA Art. 17: ICT-related incident management process An actively exploited browser zero-day (CVE-2026-125350) is present on the estate, and Google has not disclosed the delivery method or exploit effect, so detection depends on the firm's own process. The incident management process must be able to detect and respond to exploitation of a browser flaw whose vector is unknown; confirm endpoint telemetry covers Chrome crash and renderer behaviour before, not after, an alert.
DORA Art. 19: reporting of major ICT-related incidents to competent authorities If exploitation of CVE-2026-125350 on a firm's estate meets the major-incident threshold, it is reportable; the trigger is confirmed compromise, not the patch itself. Pre-agree the classification decision and evidence needed so a confirmed browser compromise can be reported within the regulatory timeline; a patched-but-unexploited estate does not trigger this.
NIS2 Art. 21(2)(d): supply chain security measures The flaw is in Google Chrome, a third-party product the firm depends on, and the fix depends on the vendor's rollout reaching each endpoint. Supply chain measures must cover how browser updates are verified as applied across the estate, including endpoints where automatic update has stalled.

3. Technical analysis & attack chain

The confirmed sequence, from Google's advisory as reported:

  1. Google was notified of the vulnerability by an unnamed third party on November 6, 2026.
  2. Google issued the Stable channel update on November 9, 2026, covering Windows, Mac, Linux and Android.
  3. Google states it is "aware that an exploit for CVE-2026-125350 exists in the wild."

That is the extent of what is confirmed. Google has not published the delivery method, the targets, the attackers, or what the exploit achieves. The vulnerability is a use-after-free in Chrome's XML component: the program continues to use a pointer to memory that has already been freed, which can corrupt memory and, in some cases, let an attacker run their own code. The XML component processes structured web content, so the plausible delivery surface is a crafted page rendered in the browser, but no source states the vector and Adverse Trace does not assert one.

The update carries nine fixes in total. Beyond CVE-2026-125350, The Register reports high-severity flaws affecting WebGL, FileSystem, GPU, Compositing and the V8 JavaScript engine, and a second use-after-free in the XML component, CVE-2026-125346, reported by Arni Hardarson of Neonix Security in October. Google has not indicated that CVE-2026-125346 is exploited. HKCERT's bulletin says some of the fixed vulnerabilities could allow denial of service, security restriction bypass and remote code execution; it does not attribute those effects to CVE-2026-125350 specifically.

Google is withholding further technical detail until enough users have installed the fix, its usual practice to deny other attackers a working exploit. The practical consequence for defenders is that there is no signature to hunt on: the only reliable control is confirming the browser version on each endpoint.

This is the eighth actively exploited Chrome zero-day of 2026, matching the 2025 total, per The Register. That count is context, not a fact about this exploit.

4. Mitigation & containment

P1 within 24h

  • Confirm Chrome is at 157.0.8103.50 or 157.0.8103.51 on Windows and Mac, 157.0.8103.50 on Linux, and 157.0.8103.50 on Android, across the estate. Query endpoint management for the installed Chrome version and treat any endpoint below these as exposed.
  • Force the update where automatic rollout has not reached the endpoint: in Chrome, open About Google Chrome from the Settings or Help menu, let it check for and download the update, then click Relaunch. Push the same through your software deployment tooling for managed fleets.
  • On Android, direct users to Google Play to take 157.0.8103.50; Google says it carries the same security fixes as the desktop release unless otherwise noted.
  • Identify endpoints where update has stalled, for example where the browser is never closed or an extension is blocking the update, and remediate those individually.

P2 within 72h

  • Report the count of endpoints still below the fixed versions to the vulnerability management owner, with the list of exceptions and the reason each is stuck.
  • For endpoints that cannot be updated immediately, restrict browsing to an approved set and block unapproved sites at the secure web gateway; this reduces the crafted-page surface without claiming to close the flaw.

P3 within 7 days

  • Add a standing check that flags any Chrome install below the current Stable version, so the next zero-day does not depend on a manual sweep.
  • Review whether browser version is captured in the asset inventory used for third-party risk reporting on Google as a supplier.

No fixed release is named for any product other than Chrome. No workaround short of updating is named in public reporting.

5. Indicators of compromise

No indicators of compromise available in the source material.

The sources give no file hashes, domains, IP addresses, URLs, filenames or command lines associated with exploitation of CVE-2026-125350. Google has withheld the technical detail. There are no atomic indicators to publish and no behavioural indicators specific to this exploit in the sources; the only observable is the browser version, which is a patch-state check, not an indicator of compromise.

6. Detection

Insufficient indicators to author detection rules.

The sources contain no artefact of the exploit itself: no strings, filenames, command lines, registry keys or network values. A rule built on the CVE identifier or the product name would detect reporting about the flaw, not the exploit, so none is emitted. Detection for now rests on the version check in §4.

7. Sources

  • 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, 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
  • 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

8. Adverse Trace position

Adverse Trace assesses CVE-2026-125350 as a high-severity, actively exploited Chrome zero-day on Google's own rating; NVD has not scored it, no EPSS value is recorded, and it is not in CISA KEV, so the exploitation state rests on Google's statement alone. The client impact for EMEA financial services is moderate and time-bound: the fix shipped on November 9 and the residual risk sits entirely in endpoints that have not taken 157.0.8103.50/.51, with the caveat that Google has disclosed neither the delivery method nor the exploit's effect, so we cannot say what a successful exploit achieves. No actor is named by any source and we make no attribution. We will monitor for Google's technical disclosure once the patch has propagated and for any reporting that names a delivery vector or in-the-wild victim, and we will reissue this advisory if either appears. Clients should treat the version confirmation in §4 as the priority action and report their unpatched count back to us so we can track sector exposure.


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