Description
@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.
References6
- github.com/grpc/grpc-node/commit/350de32860428cc62473a00bee4035…
- github.com/grpc/grpc-node/commit/7c5c5181159c6ddd292805881ef2cd…
- github.com/grpc/grpc-node/commit/e8329b122ca99ba10877e990c2f6ed…
- github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.13.6
- github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.14.5
- github.com/grpc/grpc-node/security/advisories/GHSA-f596-whhp-79…
Metrics
- CVSS 3.1
-
3.7
LOW
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N - EPSS — exploit probability
- 0% percentile: 17 · as of 9 November 2026
- CWE
- CWE-550
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.