CVE-2026-11103 is a local privilege escalation vulnerability in the Google Chrome Installer on Windows affecting versions prior to 149.0.7827.53. The issue is attributed to an inappropriate implementation in the installer, which allows a local attacker to leverage a malicious file to obtain elevated operating system privileges. The vulnerability is confined to the Windows installer component rather than general web content processing, and exploitation requires local access to the target system.
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 CVE-2026-11103, demonstrating a GraphQL rate-limit bypass via field aliases. It contains two code files: a vulnerable Node.js demo server (graphql_rate_limit_server.js) and a Python exploit client (exploit_graphql_alias_bypass.py), plus a README and license. The server uses Express with express-graphql, exposes a single Query field named 'secret', and applies a naive global rate limiter that increments once per HTTP request and blocks after 5 requests. The exploit sends a single POST request to http://localhost:4000/graphql containing one GraphQL document with six aliases (a1-a6) all resolving the same 'secret' field. This causes six backend field resolutions and returns six copies of the secret while only consuming one rate-limit unit. The exploit does not provide code execution or persistence; its capability is limited to bypassing request-based throttling for data extraction or resource amplification. Overall, the repository’s purpose is educational/demonstrative: to show how GraphQL aliasing can defeat simplistic per-request rate limiting and potentially enable information disclosure or denial-of-service conditions.
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.
2 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.