Sandbox escape in Google Chrome ANGLE/GPU
CVE-2025-6558 is a high-severity vulnerability in Google Chrome caused by insufficient validation of untrusted input in the ANGLE and GPU components. It affects Chrome prior to 138.0.7204.157. Google states that a remote attacker can trigger the issue via a crafted HTML page and potentially achieve a sandbox escape. Supporting reporting further characterizes the flaw as improper/incorrect validation of untrusted input in Chrome’s graphics processing path, with exploitation observed in the wild. Additional context indicates the issue was addressed in ANGLE with added validation and, in observed exploit chains, targeted the Mali GPU user-land library.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a proof-of-concept (PoC) exploit for CVE-2025-6558, which targets a memory leak vulnerability in browsers supporting WebGL2. The repository contains three files: a LICENSE, a minimal README, and the main exploit file 'cve-2025-6558.html'. The exploit is implemented as an HTML file with embedded JavaScript. It creates a WebGL2 context, compiles custom shaders, and uses transform feedback to attempt an unsafe write to a buffer. If the browser is vulnerable, this operation is not blocked, allowing the attacker to leak memory contents as float values. The exploit logs diagnostic information and demonstrates the leak by reading back and displaying the float-encoded memory value. There are no hardcoded network endpoints or external resources; the exploit is self-contained and must be loaded in a browser. The code is a clear PoC and does not include weaponized or automated exploitation features.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
119 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Chrome/Safari ANGLE/GPU incorrect input validation vulnerability exploited as a zero-day, enabling sandbox escape (per summary).
Memory corruption in Chrome ANGLE/GPU components leading to remote code execution.
A vulnerability in Chrome's ANGLE and GPU components allowing sandbox escape via insufficient input validation, enabling attackers to break out of browser isolation.
A Chrome zero-day vulnerability referenced as actively exploited, reported by Google TAG.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.