CVE-2026-5279 is a high-severity memory corruption vulnerability in the V8 JavaScript engine used by Google Chrome. The issue is described as object corruption in V8 and affects Google Chrome versions prior to 146.0.7680.178. A remote attacker can trigger the flaw by causing the browser to process a crafted HTML page, leading to corruption of V8-managed objects during JavaScript execution. Successful exploitation can result in arbitrary code execution within the browser sandbox.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-rated object corruption vulnerability in Chrome's V8 JavaScript engine.
An object corruption vulnerability in Chrome V8 engine patched in this release.
A high-severity object corruption vulnerability in Chrome V8.
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.