CVE-2020-16040

Exp

Insufficient data validation in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Published: 2021-01-08 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-16040 is rated High Exploit Risk (74.5/100): CVSS Medium severity, with high exploitation likelihood (EPSS 74.06%, 99th percentile). 3 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-16040

EDB-ID Source Kind Published Link
49745 exploit_db edb 2021-04-06 Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-16040

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-02 75.15% 74.06% -1.08%
2 2026-05-01 75.50% 75.15% -0.35%
3 2026-04-21 — 75.50% —

Full EPSS history (80 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-16040

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2020-16040

OS Trackers for CVE-2020-16040

vendor priority summary link
debian not yet assigned CVE-2020-16040 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-16040
gentoo normal CVE-2020-16040: 1 GLSA(s) (202012-05), 2 atom(s) (www-client/chromium, www-client/google-chrome); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-16040
ubuntu medium CVE-2020-16040 medium priority: Ubuntu including 1 source packages (chromium-browser), 6 status rows across 6 suites (bionic, focal, groovy, trusty, upstream, xenial): released 3, DNE 2, not-affected 1. https://ubuntu.com/security/CVE-2020-16040

Affected software / configurations for CVE-2020-16040

Vendor Product Version Raw CPE
google chrome < 87.0.4280.88 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2020-16040

cvelogic Threat Intelligence