Heap corruption in V8 in Google Chrome
CVE-2025-12727 is a high-severity vulnerability in the V8 JavaScript engine in Google Chrome caused by an inappropriate implementation that can lead to heap corruption. Google states that Chrome versions prior to 142.0.7444.137 are affected, and that a remote attacker can trigger the issue via a crafted HTML page. Supporting advisory content indicates the flaw is reachable through web content processed by V8 and may result in memory corruption during JavaScript engine handling of attacker-controlled input. While the precise vulnerable function or code path has not been publicly disclosed, the issue is characterized as a heap corruption bug in V8 with potential for remote code execution in the browser context.
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
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity vulnerability in Chrome's V8 JavaScript engine that could allow attackers to manipulate memory and potentially execute malicious code remotely.
High-severity inappropriate implementation in Chrome’s V8 JavaScript/WebAssembly engine; V8 memory corruption/type confusion style issues are commonly leveraged for remote code execution (general risk noted).
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.