Skip to content
OpenAdvisories
High · 7.4 CVE-2026-101916 EUVD-2026-88476GHSA-m9gg-hp2v-232j

@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized

Published Sep 28, 2026 · Updated Oct 1, 2026 · Assigned by GitHub_M

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, getAuthContext does not distinguish authorized from unauthorized peer certificates when server credentials set requireClientCertificate to false. When applications use the returned authentication context, they can treat an unauthorized certificate as authorized, causing improper authentication. @grpc/grpc-js-xds can reach this condition when RBAC authentication is enabled in affected configurations. This issue is fixed in version 1.14.5 and 1.13.6.

Affected products

VendorProductAffectedFixed
grpc grpc-node < 1.13.6, >= 1.14.0, < 1.14.5 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling langfuse-3 3.225.11-r4 —
Wolfi rolling langfuse-3-worker 3.225.11-r3 —
Wolfi rolling pulumi-language-nodejs 3.268.0-r0 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm @grpc/grpc-js < 1.13.6 1.13.6 GHSA-m9gg-hp2v-232j
npm @grpc/grpc-js >= 1.14.0, < 1.14.5 1.14.5 GHSA-m9gg-hp2v-232j

Advisories 1

References