CVE-2026-48068

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 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.

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming HTTP/2 stream initiation can cause a server process created using @grpc/grpc-js to crash. This issue is fixed in versions 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 21, 2026

Advisory Details (6)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit e2c035aab2fe (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit e2c035aab2fe)

https://github.com/grpc/grpc-node/commit/e2c035aab2fe5e55d46d5fc427481497314a53a4
github_commit Patch Available

commit b1b7268f7b81 (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit b1b7268f7b81)

https://github.com/grpc/grpc-node/commit/b1b7268f7b81b92c6f03f5128dfd871c08aeb903
github_commit Patch Available

commit 455efce8acb7 (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 455efce8acb7)

https://github.com/grpc/grpc-node/commit/455efce8acb7fb249652a74c1618a6d7daf1faba
github_commit Patch Available

commit 234f9172b2ff (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 234f9172b2ff)

https://github.com/grpc/grpc-node/commit/234f9172b2ff35e586ca7d4e788557aad5985668
github_commit Patch Available

commit 1cf4bfa738b1 (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 1cf4bfa738b1)

https://github.com/grpc/grpc-node/commit/1cf4bfa738b15e59cc3daf49ffa24c04f9b626f7
github_commit Patch Available

commit 058665a6c6da (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 058665a6c6da)

https://github.com/grpc/grpc-node/commit/058665a6c6dae445e2ab0f3f6259164fac52ee17

Patch Availability(8)

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@grpc/grpc-js1.14.4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 36× 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 130 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48068?
CVE-2026-48068 is a high vulnerability published on June 11, 2026. @grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming HTTP/2 stream initiation can cause a server process created using @grpc/grpc-js to crash. This issue is fixed in…
When was CVE-2026-48068 disclosed?
CVE-2026-48068 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48068 actively exploited?
CVE-2026-48068 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 51.9% of all scored CVEs.
What is the CVSS score of CVE-2026-48068?
CVE-2026-48068 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48068, 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-48068

Explore →

Is Your Infrastructure Affected by CVE-2026-48068?

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