Improper Verification of Cryptographic Signature Affecting ratify-fips package, versions <1.4.0-r9
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-15067956
- published24 Jan 2026
- disclosed22 Jan 2026
Introduced: 22 Jan 2026
NewCVE-2026-23992 (opens in a new tab)How to fix?
Upgrade Chainguard ratify-fips to version 1.4.0-r9 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.
go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, a compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. This can lead to unauthorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. Version 2.3.1 fixes the issue. As a workaround, always make sure that the TUF metadata roles are configured with a threshold of at least 1.