Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2022-4262: Type Confusion in Google Chrome V8

Published Dec 2, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS23.5%98th percentile
CISA KEVYesAdded Dec 5, 2022
In the wildActivePer CISA KEV
Vendor
Google
IdentifiersCVE-2022-4262CWE-843 · Access of Resource Using…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Exposure surface

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.

VendorProductType
GoogleChromeapplication
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.