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 52% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
39(Track)
EG Risk 39/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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.
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 / EcosystemFixed in / 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 rangeFixed inDependents
nodejs—22.23.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.17.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.17.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 24.18.0+dfsg+~cs24.13.2-1 (87 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (42 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions)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 38× in last 7d / 161× 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 223 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48619, 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-48619

Explore →

Is Your Infrastructure Affected by CVE-2026-48619?

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

Start Free Scan →Browse All CVEs