CVE-2026-48619

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-26) is not newer than that change (2026-10-25), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-39607 (ENISA EUVD) · GHSA-v3cq-r2f8-qmmc (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • 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
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 26, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available.
Web page

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

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:22-9060020260804140259.rhel92026-08-10redhat
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_02026-07-14redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-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 10× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 338 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 238 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48619?
CVE-2026-48619 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-48619 published?
The CVE record for CVE-2026-48619 was published on June 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
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 (50th 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.