CVE-2022-1364: Google Chrome V8 Turbofan type confusion allows heap corruption

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 17 September 2026. Confidence: high.

high priorityThe flaw is a remotely reachable browser engine memory corruption issue with confirmed exploitation in CISA KEV, though it requires user interaction and a patch has long been available.

What it is

Google Chrome before 100.0.4896.127 contains a type confusion flaw in the V8 Turbofan compiler. A crafted HTML page can trigger the confusion and potentially corrupt the heap, making this a browser-engine memory safety issue that matters because Chrome is widely deployed and the flaw was exploited in the wild.

Impact

An attacker who gets the page rendered can potentially achieve heap corruption, which in a browser engine typically opens the path to code execution in the renderer process. The record does not state the exact post-exploitation outcome beyond potential heap corruption.

Attack surface

Reached over the network by loading a crafted HTML page; the CVSS vector shows no privileges required but user interaction required, so a victim must open or be directed to the page. No authentication is needed.

Exploitation

Listed in CISA KEV with a 2022-04-15 addition and 2022-05-06 remediation due date, and references are tagged Exploit, indicating known exploitation. EPSS 30-day probability is 0.1372 (96.3rd percentile), so exploitation is plausible and observed rather than theoretical.

What to do

• Update Chrome to 100.0.4896.127 or later per the vendor release notes, and verify version compliance across managed endpoints.
• Apply the referenced Gentoo GLSA update if Chromium is installed from Gentoo packages.
• Enforce automatic browser updates and block or prompt on outdated Chrome versions.
• Reduce exposure by restricting untrusted web browsing and isolating high-risk browsing in a separate environment.
• Track CISA KEV remediation deadlines and confirm closure for internet-facing browser fleets.

Detection

• Monitor for Chrome renderer crashes or abnormal process terminations that could indicate type confusion exploitation attempts.
• Hunt proxy and DNS logs for access to known malicious or exploit-hosting domains serving crafted HTML pages.
• Check endpoint telemetry for suspicious child processes spawned from Chrome renderer processes.
• Audit installed Chrome versions against 100.0.4896.127 to find unpatched hosts.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.