CVE-2026-48937

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-06-18. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a GOAWAY frame. This vulnerability affects two supported release lines: Node.js 22 and Node.js 24.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity53% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 22, 2026

Advisory Details (2)

Auto-updated Jun 18, 2026
No patch confirmed yet.
generic

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

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

HackerOne

https://hackerone.com/reports/3658225

Vendor Advisories for CVE-2026-48937(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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-27 22:09 UTCEG score recompute
  2. 2026-07-27 22:09 UTCGHSA enrichment
  3. 2026-07-26 17:18 UTCEG score recompute
  4. 2026-07-26 17:18 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:18 UTCEG score recompute
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 02:29 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-17 03:19 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 01:15 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 23:11 UTCGHSA enrichment
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 21:02 UTCGHSA enrichment
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 45 more
  1. 2026-07-12 18:58 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 16:53 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-10 14:49 UTCGHSA enrichment
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 12:45 UTCGHSA enrichment
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 10:41 UTCGHSA enrichment
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 08:37 UTCGHSA enrichment
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 06:27 UTCGHSA enrichment
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 04:09 UTCGHSA enrichment
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 01:54 UTCGHSA enrichment
  19. 2026-07-02 23:47 UTCGHSA enrichment
  20. 2026-07-01 21:43 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 19:40 UTCGHSA enrichment
  24. 2026-06-29 17:37 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-28 15:32 UTCGHSA enrichment
  28. 2026-06-28 14:07 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-28 04:56 UTCEPSS rescore
  31. 2026-06-27 13:28 UTCGHSA enrichment
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-26 11:24 UTCGHSA enrichment
  34. 2026-06-25 13:49 UTCEPSS rescore
  35. 2026-06-25 07:58 UTCGHSA enrichment
  36. 2026-06-24 14:05 UTCEPSS rescore
  37. 2026-06-24 05:54 UTCGHSA enrichment
  38. 2026-06-23 21:33 UTCEPSS rescore
  39. 2026-06-23 21:33 UTCEPSS rescore
  40. 2026-06-23 03:48 UTCGHSA enrichment
  41. 2026-06-22 01:40 UTCGHSA enrichment
  42. 2026-06-20 23:34 UTCGHSA enrichment
  43. 2026-06-19 21:28 UTCGHSA enrichment
  44. 2026-06-18 19:24 UTCEG score recompute
  45. 2026-06-18 19:23 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48937?
CVE-2026-48937 is a medium vulnerability published on June 18, 2026. A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a GOAWAY frame. This vulnerability affects two supported release lines: Node.js 22 and Node.js 24.
When was CVE-2026-48937 disclosed?
CVE-2026-48937 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48937 actively exploited?
CVE-2026-48937 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 58.2% of all scored CVEs.
What is the CVSS score of CVE-2026-48937?
CVE-2026-48937 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-48937?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48937, 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-48937

Explore →

Is Your Infrastructure Affected by CVE-2026-48937?

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

Start Free Scan →Browse All CVEs