CVE-2020-16040

MEDIUMNVD 6.59.0
EchelonGraph scoreMEDIUM confidence

Score elevated to 9.0 because EPSS predicts 100% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 4 sources updated this weekWeaponized
6.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 100%
CISA-KEV: Not listedEPSS: 100%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
9.0(medium)
EG Risk
85(Track)
EG Risk 85/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.9%
KEV
Not listed

Published

January 8, 2021

Last Modified

November 21, 2024

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:14 UTCEPSS rescore
  2. 2026-07-23 01:50 UTCEG score recompute
  3. 2026-07-22 21:28 UTCEG score recompute 2.50
  4. 2026-07-22 21:28 UTCGHSA enrichment
  5. 2026-07-19 04:22 UTCOSV refresh
  6. 2026-07-13 22:27 UTCEPSS rescore
  7. 2026-07-13 22:27 UTCEPSS rescore
  8. 2026-07-01 10:48 UTCOSV refresh
  9. 2026-06-15 17:46 UTCEPSS rescore
  10. 2026-06-14 23:15 UTCEPSS rescore
  11. 2026-06-13 22:58 UTCEPSS rescore
  12. 2026-06-13 22:58 UTCEPSS rescore
  13. 2026-06-13 17:13 UTCOSV refresh
  14. 2026-06-12 23:10 UTCEPSS rescore
  15. 2026-06-11 13:58 UTCEPSS rescore
  16. 2026-06-10 22:16 UTCEPSS rescore
  17. 2026-06-10 22:16 UTCEPSS rescore
  18. 2026-06-10 13:20 UTCEPSS rescore
  19. 2026-06-08 14:15 UTCEPSS rescore
  20. 2026-06-08 14:15 UTCEPSS rescore
  21. 2026-06-07 15:23 UTCEPSS rescore
  22. 2026-06-07 15:23 UTCEPSS rescore
  23. 2026-06-05 22:45 UTCEPSS rescore
  24. 2026-06-05 22:45 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
Show 17 more
  1. 2026-06-05 06:08 UTCEPSS rescore
  2. 2026-06-02 20:11 UTCEPSS rescore
  3. 2026-06-02 20:11 UTCEPSS rescore
  4. 2026-06-01 13:50 UTCEPSS rescore
  5. 2026-06-01 13:50 UTCEPSS rescore
  6. 2026-05-31 00:15 UTCEPSS rescore
  7. 2026-05-31 00:15 UTCEPSS rescore
  8. 2026-05-29 13:42 UTCEPSS rescore
  9. 2026-05-28 13:43 UTCEPSS rescore
  10. 2026-05-28 13:43 UTCEPSS rescore
  11. 2026-05-27 13:39 UTCEPSS rescore
  12. 2026-05-26 22:28 UTCEG score recompute
  13. 2026-05-26 22:28 UTCGHSA enrichment
  14. 2026-05-26 13:42 UTCEPSS rescore
  15. 2026-05-26 13:42 UTCEPSS rescore
  16. 2026-05-25 11:16 UTCOSV refresh
  17. 2026-05-24 16:48 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-49745
    First seen Apr 6, 2021

    Google Chrome 86.0.4240 V8 - Remote Code Execution

    Open source ↗
  • Metasploitexploit/multi/browser/chrome_simplifiedlowering_overflow✓ verified
    First seen Nov 19, 2020

    Google Chrome versions before 87.0.4280.88 integer overflow during SimplfiedLowering phase

    Open source ↗

Frequently asked(5)

What is CVE-2020-16040?
CVE-2020-16040 is a medium vulnerability published on January 8, 2021. 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.
When was CVE-2020-16040 disclosed?
CVE-2020-16040 was first published in the National Vulnerability Database on January 8, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-16040 actively exploited?
CVE-2020-16040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-16040?
CVE-2020-16040 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2020-16040?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-16040, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-16040

Explore →

Is Your Infrastructure Affected by CVE-2020-16040?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.