Loading vulnerability…
CVE-2026-11120 is an insufficient input validation vulnerability in Enterprise Reporting in Google Chrome prior to 149.0.7827.53. The flaw allows untrusted input to be processed with inadequate validation in a security-sensitive browser component. An attacker who has already achieved compromise of the renderer process can leverage a crafted HTML page to potentially escape Chrome's sandbox, crossing a key browser security boundary and enabling access beyond the restricted renderer context.
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.
Small 4-file proof-of-concept repository demonstrating command injection in a CI/CD build workflow, labeled as CVE-2026-11120. The main vulnerable component is `cicd_build.py`, which constructs `git clone {repo_url} /tmp/repo` and executes it with `subprocess.check_call(..., shell=True)`. Because the repository URL is attacker-controlled and unsanitized, shell metacharacters can append arbitrary commands. The included demo payload uses `https://github.com/org/repo.git; id > /tmp/pwned`, resulting in execution of `id` on the build host and creation of `/tmp/pwned`. `exploit_git_injection.py` appears intended as a helper script to trigger the vulnerable script and read the proof file, though it is incomplete/buggy because it calls `subprocess.run` without importing `subprocess` and imports `requests` without using it. Repository structure: `README.md` explains the vulnerability and demo steps; `cicd_build.py` contains the vulnerable logic and embedded exploit string; `exploit_git_injection.py` is a secondary launcher/verification script; `LICENSE` is standard MIT. Overall purpose: demonstrate arbitrary command execution via malicious Git URL injection in insecure CI/CD automation.
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.