Loading vulnerability…
CVE-2026-11645 is an out-of-bounds read and write vulnerability in the V8 engine in Google Chrome versions before 149.0.7827.103. A remote attacker can trigger the flaw through a crafted HTML page and execute arbitrary code inside the browser sandbox. The vulnerability also affects Chromium-based Microsoft Edge and Opera releases incorporating vulnerable code. It was actively exploited as a zero-day and patched in June 2026.
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 (2 hidden).
This repository is a very small standalone browser PoC consisting of one HTML file and one README. The main artifact, CVE-2026-11645.html, is a self-contained client-side test page with buttons for version checking, repeated trigger execution, and an automated stress loop. Its JavaScript checks navigator.userAgent for the Chrome major version, labels versions below 149 as likely vulnerable, and then runs a trigger routine that repeatedly instantiates a class extending Function while changing a property value from an integer to a floating-point number. The code frames this as a V8 type confusion / out-of-bounds memory corruption trigger and is designed to induce a crash or instability in vulnerable Chrome 148 builds. There are no network callbacks, no external exploit servers, no shell payloads, and no persistence or command execution logic. The exploit capability is limited to local-in-browser triggering of the claimed vulnerability when a victim opens the malicious HTML page. The strongest observable outcome supported by the code is browser crash/stress testing; the README discusses possible RCE impact, but the repository does not include a full exploitation chain or arbitrary code execution payload. Overall, this is best classified as a browser/web proof-of-concept trigger for a claimed Chrome V8 memory corruption issue, not a weaponized exploit.
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.
219 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A recently disclosed Google Chrome vulnerability used in a controlled research evaluation, where GLM-5.3-Flash combined it with another known flaw to create an ARM64 exploit chain.
An out-of-bounds memory access vulnerability in Chrome's V8 JavaScript engine, listed as a previously patched zero-day exploited in the wild. The article reports a CVSS score of 8.8.
A previously fixed Chrome zero-day vulnerability reported as actively exploited.
A previously patched Chrome zero-day vulnerability from 2026; no further technical details are provided.
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.