Loading vulnerability…
CVE-2026-11113 is an insufficient validation of untrusted input vulnerability in ANGLE in Google Chrome versions earlier than 149.0.7827.53. An attacker who has already compromised the Chrome renderer process may use a crafted HTML page to potentially escape 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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone proof-of-concept/demo for CVE-2026-11113, showing SMTP header injection in a vulnerable contact form. It contains two Python files: a vulnerable Flask server (contact_form_server.py) and a client-side exploit script (exploit_smtp_header_injection.py), plus a README and license. The server exposes a POST /contact route and unsafely interpolates request.form['email'] directly into raw mail headers using CRLF-delimited strings. The exploit script sends a POST request to http://localhost:5000/contact with an email value containing CRLF characters followed by a Bcc header, causing additional recipients to be inserted into the generated message. The included server only prints the resulting message instead of actually sending mail, so the repository demonstrates the vulnerability mechanics rather than delivering a full real-world mail relay exploit. Overall, this is a valid web attack PoC with a basic hardcoded payload demonstrating unauthorized email recipient injection for spam/phishing abuse.
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.
2 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.