Loading vulnerability…
CVE-2026-9997 is a use-after-free vulnerability in the Input component of Google Chrome and Chromium before version 148.0.7778.216. An attacker who has already compromised the browser renderer process can use a crafted HTML page to potentially escape the browser sandbox. The memory-safety flaw can cause memory corruption and may enable arbitrary code execution in the browser context.
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.
Small 4-file proof-of-concept repository demonstrating a VPN split-tunneling bypass via DHCP option injection, labeled as CVE-2026-9997. The repository contains two Python scripts and supporting README/LICENSE files. `rogue_dhcp_server.py` is a minimal simulation stub for a rogue DHCP server; it does not implement full packet crafting or network transmission, but documents the intended behavior of sending a DHCP OFFER containing Option 121 (Classless Static Route) to influence victim routing. `vpn_client_sim.py` is the functional part of the demo: it invokes the Linux `ip route add` command to install a route for `10.0.0.0/8` via attacker gateway `192.168.1.100`, illustrating how traffic to a sensitive subnet could be diverted off-VPN. There is no real DHCP server implementation, no raw socket/scapy logic, and no post-exploitation payload beyond route manipulation, so this is best classified as a POC rather than an operational exploit. Main capability: network-based route injection/bypass of VPN policy leading to traffic leakage or exfiltration opportunities on the same LAN.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.