CVE-2025-68121 Affecting ratify-fips package, versions <1.4.0-r12


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (2nd 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-RATIFYFIPS-15258227
  • published11 Feb 2026
  • disclosed5 Feb 2026

Introduced: 5 Feb 2026

NewCVE-2025-68121  (opens in a new tab)

How to fix?

Upgrade Chainguard ratify-fips to version 1.4.0-r12 or higher.

NVD Description

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

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

CVSS Base Scores

version 3.1