TechWhoKnows
Log inSign up
Latest
AI
Startups
Venture
Tech
Security
Hardware
Biotech & Climate
Markets & Policy
Companies
TopicsNewsletterAbout
TechWhoKnows

Independent tech news from Singapore, with the sources linked.

Sections

  • AI
  • Startups
  • Venture
  • Tech
  • Security
  • Hardware
  • Biotech & Climate
  • Markets & Policy

TechWhoKnows

  • Companies
  • About
  • Newsletter
  • All topics
  • Search
  • Account

© 2026 TechWhoKnows. All rights reserved.

  • Privacy
  • Terms
Home/Security/Zero-Days & Patching

Google Issues Emergency Chrome Patch for Actively Exploited XSLT Sandbox Escape CVE-2026-125350

Google has released an urgent patch for Chrome across all platforms to fix CVE-2026-125350, an actively exploited high-severity use-after-free flaw.

Google Issues Emergency Chrome Patch for Actively Exploited XSLT Sandbox Escape CVE-2026-125350

By Elena Rostova, Cybersecurity

15 Nov 2026, updated 16 Nov7 min read

Critical Use-After-Free in Chrome Core Component

Google has pushed an urgent security release for its Chrome browser across desktop and mobile channels, addressing an actively exploited zero-day vulnerability registered as CVE-2026-125350. The vulnerability resides inside Chrome's Extensible Stylesheet Language Transformations (XSLT) parsing component, a core sub-system responsible for processing structured XML documents and transforming them into readable web presentations.

According to technical advisories released by the Google Chromium security engineering team, the flaw is classified as a high-severity use-after-free memory corruption condition. When a user navigates to an adversary-controlled web page or interacts with an untrusted embedded iframe, specifically structured XSLT stylesheets cause the browser memory allocator to free an active internal DOM node prematurely. Subsequent operations reuse the dangling pointer, granting an unauthenticated attacker the ability to execute arbitrary code within the sandboxed Chrome renderer process.

Google noted in its security bulletin that an exploit for CVE-2026-125350 exists in the wild. While Google restricts access to bug details and technical reproduction repositories until a decisive majority of enterprise and consumer installations apply the fix, telemetry from third-party threat intelligence partners indicates that the vulnerability has been weaponised in targeted operations against enterprise workstations and financial sector analysts.

Active Exploitation Chained with Sandbox Escape Vectors

While memory corruption inside the Chrome renderer process is contained by operating system-level sandboxing under standard conditions, threat actors have historically paired renderer-level use-after-free vulnerabilities with secondary local privilege escalation flaws. By chaining CVE-2026-125350 with an operating system kernel vulnerability or graphics driver bug, an attacker can break out of the browser sandbox to execute arbitrary payloads with host operating system privileges.

The flaw affects all modern versions of Chromium before build 131.0.6778.85 on Windows and macOS, alongside 131.0.6778.86 on Linux. Independent security researchers reported that the trigger mechanism does not require complex user interaction beyond standard page rendering. Merely visiting a compromised news portal or opening an HTML-formatted email attachment rendered through Chromium-based email clients can initiate the heap reallocation sequence.

Downstream browser vendors that rely on the open-source Chromium codebase, including Microsoft Edge, Brave, Opera, and Vivaldi, have initiated emergency testing pipelines to integrate Google's upstream fix into their respective stable channels. Microsoft confirmed that an emergency update for Edge will deploy globally within 24 hours of Google's release.

CISA Adds Zero-Day to Known Exploited Vulnerabilities Catalogue

Following Google's public advisory, the US Cybersecurity and Infrastructure Security Agency (CISA) updated its Known Exploited Vulnerabilities (KEV) catalogue to mandate federal remediation. CISA confirmed that CVE-2026-125350 poses an immediate threat to federal enterprise information systems, establishing a mandatory patch compliance deadline under Binding Operational Directive 22-01.

CISA's advisory notes that these types of vulnerabilities serve as frequent entry points for sophisticated threat groups seeking initial access to enterprise perimeters. Once an unauthenticated remote attacker gains stable code execution on an endpoint, subsequent phases of the attack lifecycle often involve credential harvesting from local LSASS memory, browser token theft, and lateral movement across internal corporate networks.

Security operations teams across private sector enterprises have been instructed to verify that automatic browser updates are functioning correctly across all managed endpoints. In environments where browser updates are scheduled on monthly deployment cadences, administrators are strongly advised to override release schedules and trigger immediate manual synchronisation.

Verification and Mitigation Procedures for Administrators

Enterprise systems administrators can verify compliance by checking that Google Chrome reports version 131.0.6778.85 or higher on Windows and macOS workstations, and version 131.0.6778.86 on Linux systems. On Android devices, users must install the latest package distributed through Google Play, while Chrome for iOS remains unaffected because Apple requires all third-party browsers on iOS to utilise the WebKit rendering engine rather than Chromium's Blink and V8 stacks.

For organisations operating air-gapped environments or managing legacy systems that cannot immediately restart browser processes, administrators can temporarily mitigate risk by enforcing strict content security policies (CSP) that restrict XML and XSLT document parsing on edge proxies. However, security analysts stress that proxy-level filtering cannot completely neutralize base64-encoded or encrypted payloads delivered over TLS connections.

The prompt rollout of build 131.0.6778.85 represents Google's eighth zero-day patch for Chrome during the current calendar year. IT departments should run inventory queries across fleet management systems to identify workstations with pending browser restarts, as Chrome updates downloaded in the background only take effect once the application process terminates and reopens.

Sources

  1. 1Google Chrome Releases Stable Channel Updatechromereleases.googleblog.com
  2. 2CISA Known Exploited Vulnerabilities Cataloguecisa.gov

More on

  • Google-chrome
  • Zero-days
  • CVE-2026-125350
  • CISA-kev
  • Browser-security
  • Memory-safety

Further reading

Zero-Days & Patching

CISA Orders Agencies to Patch Actively Exploited UnrealIRCd Flaw CVE-2026-114713 by 16 November

15 Nov 2026

Zero-Days & Patching

CISA Issues Emergency Patch Mandate for Check Point Gaia OS Flaw Chained With Wiper Attacks

14 Nov 2026

Zero-Days & Patching

Apache Discloses Critical mod_http2 Heap Corruption Flaw Enabling Remote Code Execution

14 Nov 2026

Zero-Days & Patching

QNAP Warns NAS Owners Over Active Plex2Shell CVE-2026-96652 RCE Attacks

16 Nov 2026

Follow TechWhoKnows for real-time coverage

Stay updated with the latest developments in technology.

XBlueskyThreadsInstagramLinkedInTikTokYouTube

The TWK Newsletter

Pick your topics and we'll email you our stories on them, with links to the sources.

In this story

Related stories

CISA Orders Agencies to Patch Actively Exploited UnrealIRCd Flaw CVE-2026-114713 by 16 November

15 Nov 2026

CISA Issues Emergency Patch Mandate for Check Point Gaia OS Flaw Chained With Wiper Attacks

14 Nov 2026

Apache Discloses Critical mod_http2 Heap Corruption Flaw Enabling Remote Code Execution

14 Nov 2026