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 services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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%
EPSS PROB
25%
EPSS %ILE
97th
KEV
Not listed

Published

March 30, 2026

Last Modified

August 19, 2026

Advisory Details (10)

Auto-updated Jul 3, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.6 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:7983
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7896
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:7675
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:7670
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7350
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:7310
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:7302
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:7123
redhatMentions a patch (unverified)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
nodejs—
  • every version up to 22.22.2-r0: fixed in 22.22.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.22.2-r0: fixed in 22.22.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.14.1-r0: fixed in 24.14.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.14.1-r0: fixed in 24.14.1-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 18.20.4+dfsg-1~deb12u1 (21 versions)
  • every version up to 18.20.4+dfsg-1~deb12u2: fixed in 18.20.4+dfsg-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1
  • every version up to 20.19.2+dfsg-1+deb13u2: fixed in 20.19.2+dfsg-1+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 22.22.1+dfsg+~cs22.19.15-1 (25 versions)
  • every version up to 22.22.2+dfsg+~cs22.19.15-1: fixed in 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 6× in last 7d / 20× 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 144 total refreshes for this CVE.

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

Related CVEs(same product + 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 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 (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-21710?
CVE-2026-21710 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-21710?
A fix for CVE-2026-21710 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-21710 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-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.

Book a Demo →Browse All CVEs