CVE-2026-21713

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-03-30. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possible, this behavior could be exploited as a timing oracle to infer HMAC values. Node.js already provides timing-safe comparison primitives used elsewhere in the codebase, indicating this is an oversight rather than an intentional design decision. This vulnerability affects 20.x, 22.x, 24.x, and 25.x.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
42
EG Risk 42/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
Severity59% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

Published

March 30, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated May 10, 2026
Patch available.
generic

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

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

Vendor Advisories for CVE-2026-21713(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs:24-8100020260408131901.6d8804032026-04-13redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat

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(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-21713?
CVE-2026-21713 is a medium vulnerability published on March 30, 2026. A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possible, this behavior…
When was CVE-2026-21713 disclosed?
CVE-2026-21713 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-21713 actively exploited?
CVE-2026-21713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-21713?
CVE-2026-21713 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-21713?
A fix for CVE-2026-21713 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-21713 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-21713

Explore →

Is Your Infrastructure Affected by CVE-2026-21713?

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

Book a Demo →Browse All CVEs