CVE-2026-95275 is an incorrect reference-resolution vulnerability in Blink's Region Capture implementation. CropTarget.fromElement() and RestrictionTarget.fromElement() cached pending ScriptPromiseResolver instances solely by DOM Element. Because that cache was not partitioned by the caller's ScriptState, V8 Realm, or DOMWrapperWorld, a subsequent call from another JavaScript world for the same element could receive a Promise created in the first caller's world. This can violate Chrome's isolated-world boundary, including between an extension content script and a webpage sharing the same DOM element.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect reference resolution vulnerability in Google Chrome MediaStream, fixed in Chrome 154.0.8037.57.
A Chrome Blink Region Capture privilege-escalation flaw in which CropTarget.fromElement() and RestrictionTarget.fromElement() could return an extension isolated-world Promise to webpage JavaScript when concurrent calls used the same DOM element. This breaks Chrome's extension isolated-world boundary, enabling disclosure and manipulation of extension-world objects and potentially abuse of extension capabilities reachable through captured callbacks.
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.