Loading vulnerability…
CVE-2026-11102 is an inappropriate implementation flaw in the Isolated Web Apps component of Google Chrome affecting versions prior to 149.0.7827.53. A remote attacker can trigger arbitrary code execution inside the Chrome sandbox by supplying a malicious file. The issue is described as a medium-severity Chromium vulnerability and appears to stem from incorrect security-relevant implementation behavior in the Isolated Web Apps feature rather than a memory corruption condition explicitly identified in the available information.
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/demo exploit for CVE-2026-11102, showing OAuth2 implicit grant fragment hijacking caused by missing redirect_uri validation. It contains two code files: a Node.js Express server (oauth_server.js) that simulates a vulnerable OAuth authorization server, and a Python script (exploit_fragment_hijack.py) that submits an authorization request with a malicious redirect_uri. The vulnerable server accepts the supplied redirect_uri and redirects to it with #access_token=secret_access_token&state=xyz appended as a fragment. The exploit demonstrates the core capability of token exfiltration to an attacker-controlled page, which could enable account takeover if a real token were issued. Repository structure is minimal: LICENSE, README.md, the vulnerable server, and the exploit script. The code is operational but basic and hardcoded, making it best classified as an operational PoC/demo rather than a weaponized exploit.
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.
4 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.