@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.
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 54% 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
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
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- —
- EPSS
- 46.2%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
July 21, 2026
Advisory Details (6)
Auto-updated Jul 15, 2026Patch available. Sources: github_commit.
github_commit Patch Available
commit e2c035aab2fe (grpc/grpc-node)
Patch available: grpc/grpc-node @grpc/grpc-js@1.13.5 (contains commit e2c035aab2fe)
https://github.com/grpc/grpc-node/commit/e2c035aab2fe5e55d46d5fc427481497314a53a4github_commit Patch Available
commit b1b7268f7b81 (grpc/grpc-node)
Patch available: grpc/grpc-node @grpc/grpc-js@1.11.4 (contains commit b1b7268f7b81)
https://github.com/grpc/grpc-node/commit/b1b7268f7b81b92c6f03f5128dfd871c08aeb903github_commit Patch Available
commit 455efce8acb7 (grpc/grpc-node)
Patch available: grpc/grpc-node @grpc/grpc-js@1.12.7 (contains commit 455efce8acb7)
https://github.com/grpc/grpc-node/commit/455efce8acb7fb249652a74c1618a6d7daf1fabagithub_commit Patch Available
commit 234f9172b2ff (grpc/grpc-node)
Patch available: grpc/grpc-node @grpc/grpc-js@1.14.4 (contains commit 234f9172b2ff)
https://github.com/grpc/grpc-node/commit/234f9172b2ff35e586ca7d4e788557aad5985668github_commit Patch Available
commit 1cf4bfa738b1 (grpc/grpc-node)
Patch available: grpc/grpc-node @grpc/grpc-js@1.9.16 (contains commit 1cf4bfa738b1)
https://github.com/grpc/grpc-node/commit/1cf4bfa738b15e59cc3daf49ffa24c04f9b626f7github_commit Patch Available
commit 058665a6c6da (grpc/grpc-node)
Patch available: grpc/grpc-node @grpc/grpc-js@1.10.12 (contains commit 058665a6c6da)
https://github.com/grpc/grpc-node/commit/058665a6c6dae445e2ab0f3f6259164fac52ee17Vendor Advisories for CVE-2026-48068(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @grpc/grpc-js | — | 1.14.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 8× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-11 13:56 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 46.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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
Is Your Infrastructure Affected by CVE-2026-48068?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.