Loading vulnerability…
CVE-2026-11111 is an out-of-bounds read vulnerability in the ANGLE component of Google Chrome before version 149.0.7827.53. A remote attacker can trigger a read outside valid memory boundaries through a crafted HTML page, potentially exposing sensitive memory contents.
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 Python proof-of-concept demonstrating a TOCTOU race condition in a Flask file server. It contains two code files: toctou_server.py, which implements the vulnerable service, and exploit_toctou.py, which performs the race. The server exposes a /read endpoint, joins a user-supplied filename to SAFE_DIR (/tmp/safe), checks os.path.isfile(filepath), sleeps for 0.2 seconds, and then opens the file. That gap creates a race window. The exploit prepares /tmp/safe/data.txt as a benign file, starts a thread that waits briefly, unlinks the file, and replaces it with a symlink to /etc/shadow, then sends a GET request to http://localhost:5000/read?file=data.txt. If timed correctly, the server opens the symlink target and returns sensitive file contents. The repository also includes a README describing the issue as CVE-2026-11111 and a LICENSE file. Overall, this is an operational local/web exploit PoC for sensitive file disclosure via symlink swap against a deliberately vulnerable Python/Flask application.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.