Loading vulnerability…
CVE-2026-15118 is a high-severity use-after-free vulnerability in the Input component of Google Chrome. In affected versions prior to 150.0.7871.115, improper object lifetime management during input processing can leave freed memory reachable by subsequent operations. A remote attacker can trigger the flaw via a crafted HTML page, and available reporting indicates exploitation may involve user interaction that causes malicious webpage content to exercise vulnerable input-handling code paths. Successful exploitation can corrupt browser memory and achieve arbitrary code execution within the Chrome 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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability in input handling fixed in ChromeOS 151.
A use-after-free vulnerability in Chrome input processing that could allow malicious webpages to corrupt browser memory after user interaction.
A high-severity use-after-free vulnerability in Chrome's Input component.
A high-severity use-after-free vulnerability in Chrome's Input component.
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.