CVE-2020-6413

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.9% (78th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 8.8Exploit: None knownExposed services: —

A fix is available — apply it.

Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass HTML validators via a crafted HTML page.

Internet exposure

The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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
Severity88% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 11, 2020

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Aug 19, 2026
Patch available. Sources: redhat.
generic

[SECURITY] [DSA 4638-1] chromium security update

https://www.debian.org/security/2020/dsa-4638
generic

Chromium, Google Chrome: Multiple vulnerabilities (GLSA 202003-08) — Gentoo security

https://security.gentoo.org/glsa/202003-08
generic

[SECURITY] Fedora 31 Update: chromium-80.0.3987.132-1.fc31 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X3B5RWJQD5LA45MYLLR55KZJOJ5NVZGP/
generic

[SECURITY] Fedora 30 Update: chromium-80.0.3987.149-1.fc30 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
generic
https://crbug.com/1005713
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6 Supplementary.

https://access.redhat.com/errata/RHSA-2020:0514

Vendor Advisories for CVE-2020-6413

Vendor advisories for this CVE are temporarily unavailable — the list could not be loaded just now. That is not a sign that none exist; please retry shortly.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatchromium-browser-0:80.0.3987.87-1.el6_102020-02-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
chromium73.0.3683.75-1 ... 80.0.3987.122-2 (25 versions)
  • every version up to 80.0.3987.132-1~deb10u1: fixed in 80.0.3987.132-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 80.0.3987.106-1: fixed in 80.0.3987.106-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 80.0.3987.106-1: fixed in 80.0.3987.106-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 80.0.3987.106-1: fixed in 80.0.3987.106-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 80.0.3987.106-1: fixed in 80.0.3987.106-1
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 27× 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.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-10-05 17:40 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:22 UTCEPSS rescore
  4. 2026-10-03 14:22 UTCEPSS rescore
  5. 2026-10-02 16:22 UTCEPSS rescore
  6. 2026-10-01 19:46 UTCEPSS rescore
  7. 2026-09-30 15:22 UTCEG score recompute
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-27 13:41 UTCEPSS rescore
  10. 2026-09-27 09:37 UTCOSV refresh
  11. 2026-09-26 15:54 UTCEPSS rescore
  12. 2026-09-26 15:54 UTCEPSS rescore
  13. 2026-09-26 00:21 UTCEPSS rescore
  14. 2026-09-24 14:00 UTCEPSS rescore
  15. 2026-09-22 14:44 UTCEPSS rescore
  16. 2026-09-21 20:28 UTCEPSS rescore
  17. 2026-09-19 15:37 UTCEPSS rescore
  18. 2026-09-18 19:23 UTCEPSS rescore
  19. 2026-09-17 19:22 UTCEPSS rescore
  20. 2026-09-16 14:04 UTCEPSS rescore
  21. 2026-09-15 03:06 UTCEPSS rescore
  22. 2026-09-13 16:43 UTCEPSS rescore
  23. 2026-09-12 14:57 UTCEPSS rescore
  24. 2026-09-08 21:56 UTCEPSS rescore
  25. 2026-09-07 19:21 UTCOSV refresh
Show 75 more
  1. 2026-09-07 15:58 UTCEPSS rescore
  2. 2026-09-06 13:44 UTCEPSS rescore
  3. 2026-09-05 15:25 UTCEPSS rescore
  4. 2026-09-04 13:57 UTCEPSS rescore
  5. 2026-09-04 13:57 UTCEPSS rescore
  6. 2026-09-04 05:03 UTCEPSS rescore
  7. 2026-09-02 14:08 UTCEPSS rescore
  8. 2026-09-01 03:32 UTCEPSS rescore
  9. 2026-08-30 19:14 UTCEPSS rescore
  10. 2026-08-30 01:19 UTCEPSS rescore
  11. 2026-08-28 21:37 UTCEPSS rescore
  12. 2026-08-27 14:21 UTCEPSS rescore
  13. 2026-08-26 14:42 UTCEPSS rescore
  14. 2026-08-21 23:45 UTCEPSS rescore
  15. 2026-08-21 04:44 UTCOSV refresh
  16. 2026-08-19 17:00 UTCEPSS rescore
  17. 2026-08-18 13:44 UTCEPSS rescore
  18. 2026-08-17 13:43 UTCEPSS rescore
  19. 2026-08-17 13:43 UTCEPSS rescore
  20. 2026-08-16 14:52 UTCEPSS rescore
  21. 2026-08-16 02:11 UTCEPSS rescore
  22. 2026-08-15 01:27 UTCEPSS rescore
  23. 2026-08-13 21:57 UTCEPSS rescore
  24. 2026-08-12 13:47 UTCEPSS rescore
  25. 2026-08-08 16:33 UTCEPSS rescore
  26. 2026-08-07 16:23 UTCEPSS rescore
  27. 2026-08-06 13:43 UTCEPSS rescore
  28. 2026-08-05 20:21 UTCOSV refresh
  29. 2026-08-05 19:14 UTCEPSS rescore
  30. 2026-08-04 15:06 UTCEPSS rescore
  31. 2026-08-04 10:34 UTCEPSS rescore
  32. 2026-08-02 02:24 UTCEPSS rescore
  33. 2026-08-01 04:12 UTCEPSS rescore
  34. 2026-07-30 16:25 UTCEPSS rescore
  35. 2026-07-30 01:27 UTCEPSS rescore
  36. 2026-07-28 15:33 UTCEPSS rescore
  37. 2026-07-26 14:52 UTCEPSS rescore
  38. 2026-07-25 14:15 UTCEPSS rescore
  39. 2026-07-24 14:15 UTCEPSS rescore
  40. 2026-07-23 14:15 UTCEPSS rescore
  41. 2026-07-23 01:54 UTCEG score recompute
  42. 2026-07-22 22:40 UTCEG score recompute
  43. 2026-07-22 14:05 UTCEPSS rescore
  44. 2026-07-21 15:22 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-20 17:04 UTCEPSS rescore
  47. 2026-07-20 17:04 UTCEPSS rescore
  48. 2026-07-19 19:18 UTCOSV refresh
  49. 2026-07-19 14:28 UTCEPSS rescore
  50. 2026-07-19 14:28 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-19 02:26 UTCEPSS rescore
  53. 2026-07-18 10:02 UTCEPSS rescore
  54. 2026-07-16 17:00 UTCEPSS rescore
  55. 2026-07-15 16:55 UTCEPSS rescore
  56. 2026-07-15 16:55 UTCEPSS rescore
  57. 2026-07-15 01:57 UTCEPSS rescore
  58. 2026-07-13 22:27 UTCEPSS rescore
  59. 2026-07-13 22:27 UTCEPSS rescore
  60. 2026-07-13 06:10 UTCEPSS rescore
  61. 2026-07-13 06:10 UTCEPSS rescore
  62. 2026-07-12 05:44 UTCEPSS rescore
  63. 2026-07-12 05:44 UTCEPSS rescore
  64. 2026-07-11 08:25 UTCEPSS rescore
  65. 2026-07-11 08:25 UTCEPSS rescore
  66. 2026-07-09 19:07 UTCEPSS rescore
  67. 2026-07-08 15:12 UTCEPSS rescore
  68. 2026-07-07 13:43 UTCEPSS rescore
  69. 2026-07-06 16:25 UTCEPSS rescore
  70. 2026-07-06 02:21 UTCEPSS rescore
  71. 2026-07-06 02:21 UTCEPSS rescore
  72. 2026-07-05 02:28 UTCEPSS rescore
  73. 2026-07-05 02:28 UTCEPSS rescore
  74. 2026-07-04 06:29 UTCEPSS rescore
  75. 2026-07-04 06:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2020-6413?
CVE-2020-6413 is a high vulnerability published on February 11, 2020. Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass HTML validators via a crafted HTML page.
When was CVE-2020-6413 disclosed?
CVE-2020-6413 was first published on February 11, 2020, 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-6413 actively exploited?
CVE-2020-6413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-6413?
CVE-2020-6413 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2020-6413?
A fix for CVE-2020-6413 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-6413

Explore →

Is Your Infrastructure Affected by CVE-2020-6413?

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

Book a Demo →Browse All CVEs