Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisoryactively-exploited-vulnerability

Chrome Patches XML Use-After-Free Flaw Reportedly Exploited in the Wild

Active Exploitation · 40 sources · Updated 1d ago · First seen Nov 10, 2026

Chrome Patches XML Use-After-Free Flaw Reportedly Exploited in the Wild

Google has patched CVE-2026-125350, a high-severity use-after-free vulnerability in Chrome’s XML component that Cryptika reports is being exploited in the wild to execute malicious code remotely. The fix is available in Chrome Stable 157.0.8103.50/.51 for Windows and Mac, 157.0.8103.50 for Linux, and Extended Stable 156.0.8078.96 for Windows and Mac. Google has not disclosed the attackers or the number of targets.

The Stable release fixes nine vulnerabilities—seven High and two Medium—while the Extended Stable update addresses 11 vulnerabilities, including ten High-severity flaws. Google is restricting access to vulnerability details until most users have received fixes, with longer restrictions possible for affected shared libraries. Security teams should prioritize deployment across managed Chrome installations, verify the installed versions, and ensure users restart Chrome to activate the fixes rather than relying on the staged rollout alone.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

21 events · Jul 20, 2026 – Nov 10, 2026
  1. Reported Nov 12, 20265d ago

    Opera releases browser updates fixing CVE-2026-125350

    Opera released updates addressing several vulnerabilities, including the zero-day CVE-2026-125350. It recommends Opera One 140.0.6074.18, Opera GX 139.0.6053.63, Opera Air 139.0.6053.62, and Opera Neon 139.0.6053.6.

    Update your browser: Security fix for Chrome zero-day CVE-2026-125350 | Opera Security
  2. Reported Nov 12, 20266d ago

    Microsoft Edge 157.0.4341.46 identified as fixed for Chromium XML zero-day

    BtCIRT’s advisory, citing ThreatDefence, identifies Microsoft Edge 157.0.4341.46 or later as fixed against CVE-2026-125350. This provides a patched-version threshold beyond Microsoft’s previously reported work on an Edge fix.

    Emergency Patch Required for Actively Exploited Google Chrome Zero-Day (CVE-2026-125350) - 20261111015 | Bhutan Computer Incident Response Team
  3. Reported Nov 11, 20266d ago

    Truesec identifies vulnerable Chrome 158 Early Stable builds and first fixed version

    Truesec identified Chrome 158 Early Stable builds below 158.0.8127.30, including Windows builds 158.0.8127.18/.19, as vulnerable to CVE-2026-125350; its Chromium source analysis identified 158.0.8127.30 as the first fixed Chrome 158 build. Scanners checking only for versions below 157.0.8103.50 could incorrectly classify these vulnerable installations as safe.

    CVE-2026-125350: Use-After-Free Zero-Day in Google Chrome - Truesec
  4. Reported Nov 10, 20268d ago

    Microsoft confirms work on Edge security fix

    Microsoft confirmed that it is working on a security fix for Edge following disclosure of the actively exploited Chromium XML vulnerability CVE-2026-125350. The reference does not report an Edge patch release.

    Chrome-Update stopft attackiertes Sicherheitsleck | heise online
  5. Reported Nov 10, 20268d ago

    Google acknowledges an in-the-wild exploit for CVE-2026-125350

    Google acknowledged that an exploit for CVE-2026-125350 exists in the wild, without identifying the attackers or the number of targets. Google withheld vulnerability details and issue-tracker access pending wider deployment of the fixes.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  6. Nov 10, 20268d ago

    Vivaldi ships desktop and Android updates following Chrome XML zero-day fix

    Vivaldi shipped desktop and Android updates dated November 10 in the rollout of Chromium-based browser fixes for CVE-2026-125350. The reference does not specify the updated Vivaldi version numbers.

    CVE-2026-125350: Google Fixes Exploited Chrome XML Zero-Day
  7. Nov 10, 20268d ago

    CISA adds CVE-2026-125350 to Known Exploited Vulnerabilities catalog

    CISA added the actively exploited Chrome XML use-after-free vulnerability CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on November 10, 2026, according to the report.

    구글 크롬, 실제 공격에 악용 중인 제로데이 취약점(CVE-2026-125350) 긴급 업데이트 권고
  8. Nov 10, 20268d ago

    CVE record specifies sandboxed code execution for Chrome XML zero-day

    The published CVE-2026-125350 record states that a remote attacker can exploit the XML use-after-free through a crafted HTML page to execute arbitrary code inside Chrome’s sandbox. Its description identifies versions before 157.0.8103.50 as affected, although the product-status section inconsistently labels that version as affected.

    CVE Record: CVE-2026-125350
  9. Nov 9, 20269d ago

    Google releases Chrome for Android update addressing exploited XML zero-day

    Google released Chrome 157.0.8103.50 for Android, stating that it includes the same security fixes as the desktop release unless otherwise noted. Those fixes include a patch for the actively exploited XML use-after-free vulnerability CVE-2026-125350.

    Update Chrome now to fix a flaw attackers are exploiting - Malware News - Malware Analysis, News and Indicators
  10. Nov 9, 20269d ago

    Google releases Stable and Extended Stable fixes for CVE-2026-125350

    Google shipped Chrome Stable 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux, fixing nine vulnerabilities including CVE-2026-125350. Extended Stable 156.0.8078.96 for Windows and Mac included the same zero-day fix among 11 security fixes.

    Chrome Releases: Extended Stable Update for Desktop
  11. Reported Nov 7, 202611d ago

    Chromium patch reveals libxslt cache use-after-free mechanism and fix

    A Chromium M157 patch documents how re-entrant evaluation in libxslt’s xsltTestCompMatchDirect function can free and replace a cached object, leaving a stale pointer that can cause a double free. The fix re-reads the cache slot after evaluation and references Chromium issues 582442907 and 572578603, without identifying a CVE.

    Log - 157.0.8103.39..157.0.8103.50 - chromium/src - Git at Google
  12. Nov 6, 202612d ago

    Anonymous researcher reports Chrome zero-day CVE-2026-125350

    An anonymous researcher reported CVE-2026-125350, a High-severity use-after-free vulnerability in Chrome’s XML component. The report describes the flaw as capable of enabling remote malicious-code execution.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  13. Nov 4, 202614d ago

    Google distributes vulnerable Chrome 158 Early Stable builds to Windows users

    Google distributed Chrome 158.0.8127.18 and 158.0.8127.19 to a small proportion of Windows users. These Early Stable builds lacked the fix for CVE-2026-125350; the first fixed Chrome 158 build was 158.0.8127.30.

    CVE-2026-125350: Use-After-Free Zero-Day in Google Chrome - Malware News - Malware Analysis, News and Indicators
  14. Oct 12, 20261mo ago

    Arni Hardarson reports XML use-after-free CVE-2026-125346

    Arni Hardarson of Neonix Security reported CVE-2026-125346, a High-severity use-after-free vulnerability in Chrome’s XML component.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  15. Oct 2, 20262mo ago

    V8 type-confusion vulnerability CVE-2026-125344 reported

    A High-severity type-confusion vulnerability in Chrome’s V8 engine, tracked as CVE-2026-125344, was reported to Google.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  16. Sep 26, 20262mo ago

    Vo Duc Thang reports GPU vulnerability CVE-2026-125342

    Vo Duc Thang reported CVE-2026-125342, a Medium-severity uninitialized-resource vulnerability in Chrome’s GPU component.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  17. Sep 18, 20262mo ago

    GPU out-of-bounds write CVE-2026-125348 reported

    A High-severity out-of-bounds write vulnerability in Chrome’s GPU component, tracked as CVE-2026-125348, was reported to Google.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  18. Sep 15, 20262mo ago

    Compositing buffer overflow CVE-2026-125343 reported

    A High-severity buffer-overflow vulnerability in Chrome’s Compositing component, tracked as CVE-2026-125343, was reported to Google.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  19. Sep 15, 20262mo ago

    FileSystem authorization vulnerability CVE-2026-125347 reported

    A High-severity incorrect-authorization vulnerability in Chrome’s FileSystem component, tracked as CVE-2026-125347, was reported to Google.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  20. Aug 21, 20263mo ago

    WebGL vulnerability CVE-2026-125345 reported to Google

    A High-severity uninitialized-resource vulnerability in Chrome’s WebGL component, tracked as CVE-2026-125345, was reported to Google.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
  21. Jul 20, 20264mo ago

    GPU vulnerability CVE-2026-125349 reported to Google

    A Medium-severity uninitialized-resource vulnerability in Chrome’s GPU component, tracked as CVE-2026-125349, was reported to Google.

    Google Chrome 0-Day Vulnerability in the Wild to Execute Malicious Code Remotely | Cryptika Cybersecurity
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Chrome
Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.