CVE-2021-21224: Type Confusion in Google Chrome V8
- Vendors
- GoogleDebian ProjectFedora Project
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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-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.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.