Answer in brief
CVE-2026-101915 records a Low severity (CVSS 3.7) vulnerability in @grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messages. The current sources do not mark it as known exploited. The current feed maps grpc/grpc-node (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps grpc/grpc-node (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| grpc/grpc-nodegeneric | <1.13.6 || >=1.14.0 <1.14.5 | 1.13.6, 1.14.5 |
Published upstream
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 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 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.
Quoted source text, attributed separately from HOL analysis.