Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2021-21224: Type Confusion in Google Chrome V8

Published Apr 26, 2021 · 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
EPSS84.2%100th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendors
GoogleDebian ProjectFedora Project
IdentifiersCVE-2021-21224CWE-843 · Access of Resource Using…

CVE-2021-21224 is a type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. In affected Chrome versions prior to 90.0.4430.85, a remote attacker can trigger incorrect type handling in V8 via a crafted HTML page containing malicious JavaScript, leading to memory corruption in the renderer process. Public and in-the-wild exploitation reporting indicates the flaw was used to obtain out-of-bounds access and build exploitation primitives such as address disclosure, fake object creation, and arbitrary read/write within the sandboxed Chromium renderer. The vulnerability enables arbitrary code execution in the renderer context and has been used as the browser-entry component of multi-stage exploit chains.

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 allows remote arbitrary code execution inside a sandboxed Chrome or Chromium renderer process. On its own, this yields execution in a constrained browser sandbox context, but it is sufficient to run attacker-controlled native payloads within the renderer and to establish a foothold for follow-on exploitation. In observed exploit chains, the vulnerability was paired with Windows kernel privilege-escalation flaws to escape the sandbox, obtain elevated or SYSTEM privileges, and deploy additional malware or ransomware.

Mitigation

If you can’t patch tonight, do this now.

Where immediate patching is not possible, reduce exposure by restricting use of unpatched Chrome or Chromium-based browsers, especially on systems exposed to untrusted web content. Enforce browser sandboxing and exploit-mitigation features, minimize local administrator rights, and harden endpoints to make post-exploitation and sandbox escape more difficult. Network and application controls that limit access to untrusted or malvertising-driven sites can reduce drive-by exploitation risk, but mitigation is not a substitute for patching.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 90.0.4430.85 or later, or to the corresponding fixed version provided by the relevant Chromium-based vendor. Apply browser updates promptly across managed endpoints, including Chromium forks that may lag upstream security fixes. Because this vulnerability has been exploited in the wild, organizations should prioritize patch deployment and verify that automatic browser updating is functioning correctly.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
Debian ProjectDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2021-21224 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 Nov 3, 2021.
Is there a public exploit for CVE-2021-21224?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2021-21224.
Is there a patch for CVE-2021-21224?
Upgrade Google Chrome to version 90.0.4430.85 or later, or to the corresponding fixed version provided by the relevant Chromium-based vendor. Apply browser updates promptly across managed endpoints, including Chromium forks that may lag upstream security fixes.
What products are affected by CVE-2021-21224?
Google Chrome, Debian Project Debian Linux, and Fedora Project Fedora.
How severe is CVE-2021-21224?
CVE-2021-21224 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 84.2% (100th 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 evidence3Every report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, 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.