Loading vulnerability…
CVE-2026-0908 is a use-after-free vulnerability in the ANGLE graphics component of Google Chrome versions before 144.0.7559.59. A remote attacker can use a crafted HTML page to potentially trigger heap corruption.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository is a small exploit-development kit centered on the claimed Chrome/Chromium ANGLE use-after-free CVE-2026-0908. It is not a turnkey remote exploit repository with a delivered HTML/JS trigger; instead it contains supporting materials for building and instrumenting a custom Chromium environment to research or weaponize a browser bug. Structure: README.md is the largest file and describes the vulnerability, affected versions, impact, and mitigation. Two Python utilities support the workflow: `copy_mojo_js_bindings.py` recursively extracts `mojo_bindings.js` and `.mojom.js` files from a Chromium build tree, and `disable_aslr.py` uses the `pefile` library to clear the ASLR flag in a Windows PE binary and save a `.noaslr` copy. Two patch files modify Chromium internals: `renderer.patch` changes Blink IndexedDB deletion to force-close connections, and `v8.patch` injects a `POCHelper` object into the JS global scope with native functions for module base lookup and arbitrary 8/16/32/64-bit memory reads/writes. Main exploit capabilities: the V8 patch is the most significant artifact. It exposes `getBaseOf`, `readBits`, and `writeBits`, which are classic post-exploitation primitives used to turn memory corruption into reliable arbitrary code execution. The ASLR-disabling script further improves exploit reliability on Windows by making module addresses predictable. The Mojo binding copier suggests intended interaction with Chromium internal IPC interfaces during exploit development. The renderer patch appears to alter browser behavior to make a race or object-lifetime condition easier to reproduce. Attack model: browser/web drive-by compromise via crafted HTML/WebGL content against vulnerable Chromium-based browsers with ANGLE enabled. The repository supports local exploit development and debugging for that scenario rather than directly delivering the malicious page itself. Assessment: this is a real exploit-support repository, not merely documentation or detection logic. Because it includes hardcoded helper primitives and environment modifications rather than a polished end-user exploit, the maturity is best classified as OPERATIONAL.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free (CWE-416) vulnerability in ANGLE within Google Chrome that could allow remote exploitation leading to heap corruption via a crafted HTML page.
A use-after-free vulnerability in ANGLE (Almost Native Graphics Layer Engine) as used by Google Chrome 144.
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.