Improper Certificate Validation Affecting pulumi-language-nodejs-fips package, versions <3.264.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.21% (10th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-PULUMILANGUAGENODEJSFIPS-20371813
  • published2 Oct 2026
  • disclosed28 Sept 2026

Introduced: 28 Sep 2026

NewCVE-2026-101916  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Minimos:latest pulumi-language-nodejs-fips to version 3.264.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream pulumi-language-nodejs-fips package and not the pulumi-language-nodejs-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

@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.