How severe is CVE-2021-4102?

CVE-2021-4102 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-4102?

Affected package information for CVE-2021-4102 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2021-4102?

No fixed version has been published for CVE-2021-4102 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2021-4102 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2021-4102, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-4102?

CVE-2021-4102 has an EPSS (Exploit Prediction Scoring System) score of 5.5%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2021-4102 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-4102 (Google Chromium V8 Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-12-15. CISA required all US federal civilian agencies to remediate this vulnerability by 2021-12-29. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2021-4102?

CVE-2021-4102 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-4102 published, and has it been updated?

CVE-2021-4102 was published on February 11, 2022 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-12-15 — agencies required to remediate by 2021-12-29

CVE-2021-4102

HIGH

Published

Feb 11, 2022

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

5.5%probability of exploitation in next 30 days

Lower Risk90th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a r…

chromereleases.googleblog.comChromeDec 2021

Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a r…

cisa.govCISADec 2021

Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a r…

chromereleases.googleblog.comGoogle-sheetDec 2021

Frequently Asked Questions

Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

O3 Security · Impact-Aware SCA

Is CVE-2021-4102 in your stack?

O3 detects CVE-2021-4102 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works