CVE-2020-8265

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 9.1%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory leading to a Denial of Service or potentially other exploits.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
57
EG Risk 57/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
Severity81% × 45%
Exploitation40% × 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
9.1%
EPSS %ILE
95th
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 public PoC (EG-KEV: elevated) · 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

January 6, 2021

Last Modified

November 21, 2024

Advisory Details (8)

Auto-updated Sep 15, 2026
Patch available.
generic

[SECURITY] [DSA 4826-1] nodejs security update

https://www.debian.org/security/2021/dsa-4826
generic

NodeJS: Multiple vulnerabilities (GLSA 202101-07) — Gentoo security

https://security.gentoo.org/glsa/202101-07
generic

Node.js — January 2021 Security Releases

https://nodejs.org/en/blog/vulnerability/january-2021-security-releases/
generic

[SECURITY] Fedora 33 Update: nodejs-14.15.4-1.fc33 - package-announce - Fedora mailing-lists

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

[SECURITY] Fedora 32 Update: nodejs-12.20.1-1.fc32 - package-announce - Fedora mailing-lists

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

Vendor Advisories for CVE-2020-8265(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunodejs-legacy (4.2.6~dfsg-1ubuntu4.2+esm2) @ xenial2026-05-26ubuntu
redhatnodejs:10-8030020210118191659.229f0a1c2021-02-16redhat
redhatnodejs:12-8030020210129141730.229f0a1c2021-02-16redhat
redhatnodejs:14-8030020210126165503.229f0a1c2021-02-16redhat
redhatrh-nodejs10-nodejs-0:10.23.1-2.el72021-02-15redhat
redhatrh-nodejs12-nodejs-nodemon-0:2.0.3-1.el72021-02-11redhat
redhatrh-nodejs14-nodejs-0:14.15.4-2.el72021-02-04redhat

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

(19 across 19 ecosystems)
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 12.20.1-r0: fixed in 12.20.1-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 12.20.1-r0: fixed in 12.20.1-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.15.4-r0: fixed in 14.15.4-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs10.15.2~dfsg-2 ... 10.21.0~dfsg-1~deb10u1 (13 versions)
  • every version up to 10.23.1~dfsg-1~deb10u1: fixed in 10.23.1~dfsg-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 12.20.1~dfsg-1: fixed in 12.20.1~dfsg-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 12.20.1~dfsg-1: fixed in 12.20.1~dfsg-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 12.20.1~dfsg-1: fixed in 12.20.1~dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 12.20.1~dfsg-1: fixed in 12.20.1~dfsg-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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 166 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2020-8265?
CVE-2020-8265 is a high vulnerability published on January 6, 2021. Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method…
When was CVE-2020-8265 disclosed?
CVE-2020-8265 was first published on January 6, 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-8265 actively exploited?
CVE-2020-8265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.1% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-8265?
CVE-2020-8265 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2020-8265?
A fix for CVE-2020-8265 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-8265 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2020-8265?

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