CVE-2026-16804 is a high-severity use-after-free vulnerability in the Input component of Google Chrome affecting versions prior to 150.0.7871.186. The flaw is triggered in browser input handling and can be reached through a crafted HTML page. Available information indicates that exploitation requires the attacker to have already compromised the renderer process, after which the memory corruption condition could be leveraged to escape Chrome’s sandbox. As a use-after-free bug, the vulnerability arises from continued use of memory after it has been freed, creating the possibility of controlled memory corruption and unintended execution flow.
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.
7 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 Chrome's input handling component.
A high-severity use-after-free vulnerability in Chrome Input. The article provides no further impact details.
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.