Use-after-free in Chromoting in Google Chrome for Windows
CVE-2026-12449 is a high-severity use-after-free vulnerability in the Chromoting component of Google Chrome on Windows prior to version 149.0.7827.155. The available advisory information states that improper lifetime management in Chromoting can lead to a use-after-free condition when processing a malicious file. On successful trigger, freed memory may be reused while still referenced, creating a memory corruption condition that can be leveraged by a local attacker. Google classifies the issue as High severity, and the published impact specifically identifies OS-level privilege escalation on Windows.
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
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity use-after-free vulnerability in Chrome's Chromoting component.
A high-severity use-after-free vulnerability in Chrome Chromoting.
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.