CVE-2022-4262: Type Confusion in Google Chrome V8
- Vendor
CVE-2022-4262 is a high-severity type confusion vulnerability in the V8 JavaScript engine in Google Chrome prior to 108.0.5359.94. The flaw resides in the V8 parser’s handling of class static initialization blocks, where use of this inside a static block could incorrectly propagate through the ExpressionScope chain and mark an enclosing function as using this. Analysis of the fix indicates the issue was addressed by introducing a FunctionParsingScope while parsing class static blocks, preventing incorrect scope propagation. This parser error could lead to inconsistent bytecode generation for the same function, particularly when V8 bytecode flushing caused bytecode to be regenerated from stored parsing results. Researchers showed that stale assumptions about context layout in nested functions could then be abused to access unintended contexts, including NativeContext-resident objects, and to swap internal Map objects in a way that produced type confusion. The resulting condition enabled powerful memory corruption primitives within V8.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can lead to heap corruption and arbitrary code execution in the context of the browser renderer by means of a crafted HTML page. Public technical analysis further indicates the bug can be developed into an out-of-bounds read/write primitive inside V8 through type confusion involving internal object maps and unexpected NativeContext access. In practical terms, this can provide a strong foundation for full browser exploitation and, when chained with additional vulnerabilities, broader compromise.
Mitigation
If you can’t patch tonight, do this now.
Apply vendor patches on an urgent basis, as this vulnerability was reported as exploited in the wild. Until updates are fully deployed, reduce exposure by restricting use of untrusted web content, isolating high-risk browsing activities, and enforcing rapid browser restart/update policies so patched engine versions are loaded. Enterprise defenders should prioritize browsers based on affected Chromium/V8 builds and monitor for exploitation attempts involving malicious web content.
Remediation
Patch, then assume compromise.
Upgrade Google Chrome to version 108.0.5359.94 or later. Chromium-based browsers incorporating the vulnerable V8 version should also be updated to vendor releases that include the upstream fix for CVE-2022-4262. For Microsoft Edge, apply the vendor security update bringing the browser to version 108.0.1462.41 or later, as applicable.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
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.
References
Frequently asked questions
- Is CVE-2022-4262 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Dec 5, 2022.
- Is there a public exploit for CVE-2022-4262?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2022-4262, the earliest disclosed Jan 24, 2024.
- Is there a patch for CVE-2022-4262?
- Upgrade Google Chrome to version 108.0.5359.94 or later. Chromium-based browsers incorporating the vulnerable V8 version should also be updated to vendor releases that include the upstream fix for CVE-2022-4262.
- What products are affected by CVE-2022-4262?
- Google Chrome.
- How severe is CVE-2022-4262?
- CVE-2022-4262 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 23.5% (98th percentile) as of Oct 16, 2026.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.