CVE-2026-21710

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-30. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 25%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A flaw in Node.js HTTP request handling causes an uncaught TypeError when a request is received with a header named __proto__ and the application accesses req.headersDistinct. When this occurs, dest["__proto__"] resolves to Object.prototype rather than undefined, causing .push() to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by error event listeners, meaning it cannot be handled without wrapping every req.headersDistinct access in a try/catch. * This vulnerability affects all Node.js HTTP servers on 20.x, 22.x, 24.x, and v25.x

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Track)
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
25%
EPSS %ILE
98%
KEV
Not listed

Published

March 30, 2026

Last Modified

August 19, 2026

Advisory Details (10)

Auto-updated Jul 3, 2026
Patch available. Sources: redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.6 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:7983
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7896
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:7675
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:7670
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7350
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:7310
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7302
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:7123
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:7080
generic

Node.js — Tuesday, March 24, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/march-2026-security-releases

Vendor Advisories for CVE-2026-21710(14)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:20-9040020260421133644.rhel92026-04-22redhat
redhatnodejs:20-9060020260422064119.rhel92026-04-22redhat
redhatnodejs:20-8100020260414073138.489197e62026-04-15redhat
redhatnodejs:22-9060020260409121057.rhel92026-04-14redhat
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs:20-9070020260409073121.rhel92026-04-13redhat
redhatnodejs:24-8100020260408131901.6d8804032026-04-13redhat
redhatnodejs:22-9070020260401095228.rhel92026-04-09redhat
redhatnodejs22-1:22.22.2-2.el10_02026-04-09redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat
redhatnodejs22-1:22.22.2-1.el10_12026-04-08redhat
redhatnodejs:22-8100020260331102257.6d8804032026-04-08redhat

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

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.22.2-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.22.2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.14.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.14.1-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 18.20.4+dfsg-1~deb12u1 (21 versions)18.20.4+dfsg-1~deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u120.19.2+dfsg-1+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 22.22.1+dfsg+~cs22.19.15-1 (25 versions)22.22.2+dfsg+~cs22.19.15-1—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-21710?
CVE-2026-21710 is a high vulnerability published on March 30, 2026. A flaw in Node.js HTTP request handling causes an uncaught TypeError when a request is received with a header named proto and the application accesses req.headersDistinct. When this occurs, dest["proto"] resolves to Object.prototype rather than undefined, causing .push() to be called on a…
When was CVE-2026-21710 disclosed?
CVE-2026-21710 was first published in the National Vulnerability Database on March 30, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21710 actively exploited?
CVE-2026-21710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25% probability of exploitation in the next 30 days, which ranks it in the top 2.2% of all scored CVEs.
What is the CVSS score of CVE-2026-21710?
CVE-2026-21710 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-21710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21710, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-21710

Explore →

Is Your Infrastructure Affected by CVE-2026-21710?

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

Start Free Scan →Browse All CVEs