CVE-2026-11115 is a use-after-free vulnerability in the Google Chrome Updater component on Windows affecting versions prior to 149.0.7827.53. The flaw can be triggered by a local attacker through a malicious file, leading to memory corruption in the updater process. Because the vulnerable component operates in a privileged OS context, successful exploitation can result in elevation of privilege from a local context to higher operating system privileges.
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 minimal proof-of-concept for CVE-2026-11115, demonstrating database connection string injection in a Python application using psycopg2. The repository contains three files: an MIT LICENSE, a README describing the issue and how to run the demo, and a single Python script, db_connector.py, which is the exploit entry point. The script defines a connect() function that reads the DB_URL environment variable and passes it directly to psycopg2.connect() without validation. It then simulates attacker control by setting DB_URL to a crafted PostgreSQL URI containing '?host=evilhost.com&sslmode=disable', causing the connection to be redirected away from the intended localhost database. The main exploit capability is outbound connection redirection via untrusted environment-controlled connection strings, which can enable attacker-controlled database connections, data exfiltration, interception, or auth/transport weakening. This is not a framework module and not merely a detection script; it is a simple standalone PoC with no advanced payload beyond demonstrating host override behavior.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.