Loading vulnerability…
CVE-2025-9864 has been rejected. According to the provided content, this CVE ID was assigned in error to a vulnerability that was both introduced and fixed before the code landed in the Chrome Stable channel, and the CVE has been withdrawn. Because the identifier was rejected, there is no valid, supported vulnerability record to describe under this CVE.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity use-after-free vulnerability in the V8 JavaScript engine, potentially enabling memory corruption and arbitrary code execution in the browser process.
Unknown (listed as a trending/high-risk CVE affecting Google Chrome; no technical details provided in the content).
A high-severity use-after-free vulnerability in Google Chrome's V8 JavaScript engine that can be triggered via a specially crafted HTML page with malicious JavaScript, potentially leading to arbitrary code execution in the Chrome renderer process.
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.