Object lifecycle issue in Chrome DevTools
CVE-2026-3539 is a high-severity object lifecycle issue in DevTools in Google Chrome affecting versions prior to 145.0.7632.159. The available advisory states that the flaw could allow heap corruption when a user is convinced to install and use a crafted malicious Chrome extension. Based on the vendor wording ('object lifecycle issue' leading to heap corruption), the vulnerability is consistent with a memory-safety flaw involving improper handling of object lifetime in the DevTools component, such as use-after-free or related stale-object access conditions. Google has restricted detailed technical information pending broad patch adoption, so specific vulnerable functions or code paths are not currently available.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.