Loading vulnerability…
CVE-2026-11114 is a use-after-free vulnerability in the Device Trust component of Google Chrome on macOS prior to version 149.0.7827.53. The flaw can be triggered through a crafted HTML page and is exploitable by a remote attacker who has already achieved compromise of the renderer process. In that post-renderer-compromise context, the memory safety error can potentially be leveraged to break out of Chrome’s sandbox on macOS. Chromium rated the issue as Medium severity.
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.
Repository contains a minimal proof-of-concept for a Node.js vm sandbox escape labeled CVE-2026-11114. There are 4 files total: a README describing the issue and usage, a Python exploit client, a vulnerable Node.js Express server, and a license file. The main exploit logic is in exploit_vm_escape.py, which sends a POST request to http://localhost:3000/eval with attacker-controlled JavaScript. That JavaScript abuses this.constructor.constructor('return this.process')() to recover the Node.js process object from the vm context, then uses process.mainModule.require('child_process').execSync('id') to execute an OS command and return its output. The sandbox_server.js file demonstrates the vulnerable pattern: it accepts JSON input, extracts req.body.code, compiles it with vm.Script, runs it in a created context, and returns the result. Overall, this is an operational PoC for remote code execution against a web-exposed Node.js vm sandbox that improperly isolates built-in constructors and global scope access.
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.