CVE-2021-21220 · Published 26 Apr 2021
Google Chromium V8
On CISA's KEV list 191 days after disclosure; 3 public exploits.
Google Chromium V8 Engine contains an improper input validation vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
CISA required action (federal due date 17 Nov 2021): Apply updates per vendor instructions.
Signals
- KEV, exploited in the wild
- yes, added 3 Nov 2021, due 17 Nov 2021
- EPSS, 30-day forecast
- 70%, 99th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 26 Apr 2021 to today
- Disclosed
- Metasploit+1 d
- KEV+190 d
190 days from the Metasploit module to the KEV listing
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 3 known · links only
GitHub PoCs 2Metasploit 1Exploit-DB 0
GitHub PoCs, by trust then stars2
- AmesianX/CVE-2021-21220Not checked
first seen by skopnix 18 Oct 2026
- security-dbg/CVE-2021-21220Not checked
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
Metasploit1
This module exploits an issue in the V8 engine on x86_x64 builds of Google Chrome before 89.0.4389.128/90.0.4430.72 when handling XOR operations in JIT'd JavaScript code. Successful exploitation allows an attacker to execute arbitrary code within the context of the V8 process. As the V8 process is normally sandboxed in the default configuration of Google Chrome, the browser must be run with the --no-sandbox option for the payload to work correctly.
ruby · first seen by skopnix 18 Oct 2026
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.