CVE-2026-11104 is an uninitialized-use vulnerability in ANGLE in Google Chrome before version 149.0.7827.53. A remote attacker who has already compromised the Chrome renderer process can use a crafted HTML page to obtain potentially sensitive information from process memory.
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 is a small standalone Python proof-of-concept repository containing two code files: a deliberately vulnerable Flask/Jinja2 application (vulnerable_app.py) and a matching exploit script (exploit_ssti_attr.py). The vulnerable app exposes a single web route '/' and reads the 'name' query parameter, then unsafely embeds it into a template string passed to render_template_string, creating a classic server-side template injection condition. The exploit script sends a GET request to http://localhost:5000/ with a Jinja2 payload that uses the |attr filter to access __class__, __mro__, __getitem__, and __subclasses__(), demonstrating bypass of simplistic keyword filtering and exposing Python internals. The returned response is truncated and printed, showing subclass enumeration that could be used to progress toward RCE primitives such as os.popen. Repository structure is minimal: LICENSE, README.md, exploit_ssti_attr.py, and vulnerable_app.py. This is a real exploit POC rather than a detection script, but it is not fully weaponized because it does not include automated command execution or a customizable post-exploitation payload.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.