@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.6 and 1.14.5, when an application method handler throws an uncaught error, the server includes its error message in the status message sent to the client. The thrown error message is transmitted to the client, causing sensitive information disclosure when the message contains sensitive data. This issue is fixed in versions 1.13.6 and 1.14.5.
CVE-2026-101915
LOWPre-NVD 3.73.7—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (14th percentile of EPSS-scored CVEs). 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
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.7Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 3.7
- EG Score
- 3.7LOWmedium confidence
- EG Risk
- 17EG Risk 17/100CISA SSVC
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 computedSeverity37% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 14th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 28, 2026
Last Modified
October 1, 2026
References (6)
- security-advisories@githubhttps://github.com/grpc/grpc-node/commit/350de32860428cc62473a00bee4035360690ffea
- security-advisories@githubhttps://github.com/grpc/grpc-node/commit/7c5c5181159c6ddd292805881ef2cdec29bb475f
- security-advisories@githubhttps://github.com/grpc/grpc-node/commit/e8329b122ca99ba10877e990c2f6edd40224fd0d
- security-advisories@githubhttps://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.13.6
- security-advisories@githubhttps://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.14.5
- security-advisories@githubhttps://github.com/grpc/grpc-node/security/advisories/GHSA-f596-whhp-79r4
Vendor Advisories for CVE-2026-101915(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.13.6 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-10-03 14:25 UTCEPSS rescore
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 15:24 UTCEG score recompute
- 2026-10-01 15:01 UTCEG score recompute
- 2026-09-30 20:02 UTCEG score recompute
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-28 20:29 UTCEG score recompute
- 2026-09-28 19:52 UTCEG score recompute
- 2026-09-28 19:51 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
5 shownnpm:@grpc/grpc-js
Frequently asked(5)
What is CVE-2026-101915?
CVE-2026-101915 is a low vulnerability published on September 28, 2026. @grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.6 and 1.14.5, when an application method handler throws an uncaught error, the server includes its error message in the status message sent to the client. The thrown error message is…
When was CVE-2026-101915 disclosed?
CVE-2026-101915 was first published on September 28, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101915 actively exploited?
CVE-2026-101915 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101915?
CVE-2026-101915 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101915?
A fix for CVE-2026-101915 is available — its CVE record says: "This issue is fixed in versions 1.13.6 and 1.14.5." The vendor advisories EchelonGraph has for CVE-2026-101915 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-101915
Is Your Infrastructure Affected by CVE-2026-101915?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.