Not Failing Securely ('Failing Open') Affecting kayenta-fips-2026.0 package, versions <2026.0.4-r11


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.2% (11th 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-CHAINGUARDLATEST-KAYENTAFIPS20260-18299988
  • published25 Jul 2026
  • disclosed6 Jul 2026

Introduced: 6 Jul 2026

CVE-2026-54291  (opens in a new tab)
CWE-636  (opens in a new tab)
CWE-757  (opens in a new tab)

How to fix?

Upgrade Chainguard kayenta-fips-2026.0 to version 2026.0.4-r11 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kayenta-fips-2026.0 package and not the kayenta-fips-2026.0 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

pgjdbc is an open source postgresql JDBC Driver. In releases 42.7.4 through 42.7.11, channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS with channel binding to plain SCRAM-SHA-256 without it, losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection can trigger the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash, because the bundled com.ongres.scram:scram-client returns an empty byte array instead of failing and pgJDBC ScramAuthenticator checks only that the server advertised a PLUS mechanism, without rejecting the empty binding or checking that the negotiated mechanism uses channel binding. This issue is fixed in version 42.7.12.

CVSS Base Scores

version 3.1