CVE-2026-48619

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

A fix is available — apply it.

A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/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%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available.
generic

Node.js — Thursday, June 18, 2026 Security Releases

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

Vendor Advisories for CVE-2026-48619(12)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-main-22.23.1-2.hum12026-07-03redhat
redhatnodejs24-main-24.18.0-0.2.hum12026-07-01redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat
redhatnodejs25-main-25.9.0-1.1.hum12026-04-10redhat

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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 24.21.0+dfsg+~cs24.13.4-1 (91 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
  • every version up to 20.19.2+dfsg-1+deb13u3: fixed in 20.19.2+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions)
  • every version up to 24.17.0+dfsg+~cs24.13.2-1: fixed in 24.17.0+dfsg+~cs24.13.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-48619?
CVE-2026-48619 is a high vulnerability published on June 26, 2026. A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
When was CVE-2026-48619 disclosed?
CVE-2026-48619 was first published on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48619 actively exploited?
CVE-2026-48619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48619?
CVE-2026-48619 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48619?
A fix for CVE-2026-48619 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48619 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-48619

Explore →

Is Your Infrastructure Affected by CVE-2026-48619?

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

Book a Demo →Browse All CVEs