CVE-2026-48619

HIGHNVD 7.55.3▼
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 7.5; sources differ by 2.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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
5.3(medium)
EPSS
47.6%
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(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs:24-9080020260626074955.rhel92026-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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 63× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 04:34 UTCVendor advisory
  9. 2026-07-17 04:34 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 03:23 UTCVendor advisory
  12. 2026-07-16 03:23 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:12 UTCVendor advisory
  15. 2026-07-15 02:12 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 00:58 UTCVendor advisory
  18. 2026-07-14 00:58 UTCGHSA enrichment
  19. 2026-07-13 22:30 UTCEPSS rescore
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-12 23:47 UTCVendor advisory
  22. 2026-07-12 23:47 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-11 22:36 UTCVendor advisory
  25. 2026-07-11 22:36 UTCGHSA enrichment
Show 38 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-10 21:25 UTCVendor advisory
  3. 2026-07-10 21:25 UTCGHSA enrichment
  4. 2026-07-09 20:14 UTCVendor advisory
  5. 2026-07-09 20:14 UTCGHSA enrichment
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 19:03 UTCVendor advisory
  8. 2026-07-08 19:02 UTCGHSA enrichment
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-07 17:50 UTCVendor advisory
  11. 2026-07-07 17:50 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 15:54 UTCVendor advisory
  15. 2026-07-06 15:54 UTCGHSA enrichment
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 14:44 UTCGHSA enrichment
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 13:26 UTCGHSA enrichment
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 12:14 UTCGHSA enrichment
  22. 2026-07-02 11:01 UTCGHSA enrichment
  23. 2026-07-01 15:07 UTCEPSS rescore
  24. 2026-07-01 09:49 UTCGHSA enrichment
  25. 2026-06-30 23:22 UTCEPSS rescore
  26. 2026-06-30 08:38 UTCGHSA enrichment
  27. 2026-06-29 14:06 UTCEPSS rescore
  28. 2026-06-29 14:06 UTCEPSS rescore
  29. 2026-06-29 07:22 UTCGHSA enrichment
  30. 2026-06-28 14:07 UTCEPSS rescore
  31. 2026-06-28 06:11 UTCGHSA enrichment
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-27 04:57 UTCGHSA enrichment
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-26 21:42 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  37. 2026-06-26 03:46 UTCEG score recompute
  38. 2026-06-26 03:46 UTCGHSA enrichment

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 47.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48619?
CVE-2026-48619 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.3.
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

Explore the affected products and dependency analysis for 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