CVE-2026-101915: @grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messages
@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.
Other sources
Impact If an application method handler crashes, the error message is included in the status message sent to the client. This can leak to the client any sensitive data that may be included in the error message. This impacts anyone using @grpc/grpc-js to run servers.
Patches This vulnerability is fixed in 1.13.6 and 1.14.5.
Workarounds This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.
— GitHub
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@grpc/grpc-jsto a version that resolves this vulnerability.Fixed in 1.14.5 - Upgrade
Upgrade
npm/@grpc/grpc-jsto a version that resolves this vulnerability.Fixed in 1.13.6 - Upgrade
Upgrade
@grpc/grpc-jsto a version that resolves this vulnerability.Fixed in 1.13.6 - Upgrade
Upgrade
@grpc/grpc-jsto a version that resolves this vulnerability.Fixed in 1.14.5 - Compensating control
Use a top-level error handler in method handlers to strip sensitive error information before sending status messages to clients.
Event History
Frequently Asked Questions
Which deployments are exposed to information disclosure?
Deployments using @grpc/grpc-js versions earlier than 1.13.6 or 1.14.5 are affected when an application method handler throws an uncaught error whose message contains sensitive data.
Does an attacker need authentication or user interaction to obtain the error message?
No authentication or user interaction is required according to the provided vector. Exploitation requires reaching a handler invocation that results in an uncaught error, and the attack complexity is rated high.
What versions remediate the issue?
The issue is fixed in @grpc/grpc-js versions 1.13.6 and 1.14.5. Upgrade to an applicable fixed version.