Intel

AIKIDO-2026-593870

@grpc/grpc-js is vulnerable to Improper Certificate Validation

CVE-2026-101916Published Sep 22, 2026
September 22, 2026

74

CVE Score

High

Improper Certificate Validation

Are you affected? Scan for Free

TL;DR

BaseServerInterceptingCall.getAuthContext() in @grpc/grpc-js returns the peer's TLS certificate data for any TLS connection without checking the socket's authorized flag. Servers that create credentials with requireClientCertificate set to false and then rely on getAuthContext for authentication, such as @grpc/grpc-js-xds RBAC policies, cannot tell an unauthorized or self-signed client certificate from an authorized one. This lets an unauthorized client be treated as though it presented a trusted certificate. The fix checks socket.authorized before returning peer certificate data from getAuthContext.

How do I fix this?

Upgrade the @grpc/grpc-js library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you configure server credentials with requireClientCertificate set to false while relying on getAuthContext for authentication or RBAC decisions.

Versions

1.14.0 - 1.14.4

Fixed in 1.14.5

Background info

@grpc/grpc-js is vulnerable to Improper Certificate Validation in versions 1.14.0 - 1.14.4.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea