Loading vulnerability…
CVE-2026-11107 is a user interface spoofing vulnerability in the Downloads component of Google Chrome affecting versions prior to 149.0.7827.53. The issue is described as an inappropriate implementation flaw that can be triggered by a crafted HTML page, allowing a remote attacker to manipulate or imitate browser UI elements associated with downloads. The vulnerability does not indicate memory corruption or code execution; instead, it enables deceptive presentation within the browser interface that could mislead users about the origin, state, or trustworthiness of download-related content or actions.
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 proof-of-concept for an IDOR condition described as CVE-2026-11107. It contains two Python files: a vulnerable Flask server (idor_server.py) and a client-side exploit script (exploit_idor_uuid.py), plus a README and license. The server creates two user objects keyed by uuid.uuid1() values and exposes them through the unauthenticated route /user/<user_id>. Because UUIDv1 embeds time-derived data and is treated as a direct object reference without authorization checks, the exploit script attempts to predict nearby identifiers by deriving a UUID integer from the current timestamp and iterating through a small range. For each candidate, it sends an HTTP GET request to http://localhost:5000/user/{candidate}; if the response is 200, it prints the discovered UUID and returned JSON data. The exploit demonstrates unauthorized data access via predictable identifiers rather than code execution. Repository structure is minimal and clearly educational/PoC-oriented, with no framework integration, no persistence, and no advanced payload beyond enumeration and data retrieval.
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.
1 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.