Loading vulnerability…
CVE-2025-6558 is a high-severity vulnerability in Google Chrome affecting the ANGLE graphics abstraction layer and GPU-related processing prior to version 138.0.7204.157. The flaw is described as insufficient or incorrect validation of untrusted input in these components. A remote attacker can trigger the issue by causing the browser to process a crafted HTML page, potentially reaching vulnerable graphics-handling paths and enabling escape from Chrome’s sandbox. Reporting and subsequent analysis indicate the issue was exploited in the wild and that the fix involved adding validation in the affected graphics path. The vulnerability has also been referenced in downstream projects that incorporate related open-source code.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains a small native proof-of-concept for CVE-2026-14382, with two C programs and a README. The exploit is not network-facing; it is a local native graphics PoC that exercises EGL/OpenGL ES state transitions to trigger memory corruption in ANGLE-related transform feedback handling. The README states the bug is believed to be a variant of CVE-2025-6558 and includes a Chromium/ANGLE fix link, Android build commands, and a sample Android tombstone showing a SIGSEGV with execution flowing into /vendor/lib/egl/libGLES_mali.so. Structure: README.md documents the vulnerability, expected crash behavior, and build commands for arm32 and aarch64. poc.c is the main 32-bit PoC. It initializes an off-screen EGL pbuffer context, compiles minimal GLES 3 shaders, enables transform feedback on gl_Position, allocates a texture and transform feedback buffer, then performs a specific sequence: bind TF1, begin transform feedback, pause TF1, switch to TF2, redefine the still-referenced TF buffer through GL_ARRAY_BUFFER with a smaller size, perform buffer writes and a texture upload, switch back to TF1, resume transform feedback, and draw again. This sequence is intended to create stale/invalid state and trigger out-of-bounds or use-after-redefinition behavior in the graphics stack. poc64.c mirrors the same logic for aarch64 but is explicitly described as only demonstrating crashability; it loops through buffer redefinitions with varying sizes and resumes transform feedback, but does not achieve controlled PC. Capabilities: the code can reliably create an EGL/GLES environment, compile shaders, manipulate transform feedback objects and buffers, and trigger a crash in vulnerable graphics implementations. It does not include a post-exploitation payload, persistence, networking, or privilege-escalation logic. Overall maturity is PoC: it demonstrates vulnerability reachability and memory corruption/crash, with the 32-bit variant apparently closer to a controllable primitive, but it is not a weaponized exploit.
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.
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.
121 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.
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.