Reachable Assertion Affecting ratify-fips package, versions <1.4.0-r9


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (5th 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-15067965
  • published24 Jan 2026
  • disclosed22 Jan 2026

Introduced: 22 Jan 2026

NewCVE-2026-23991  (opens in a new tab)
CWE-617  (opens in a new tab)
CWE-754  (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, if the TUF repository (or any of its mirrors) returns invalid TUF metadata JSON (valid JSON but not well formed TUF metadata), the client will panic during parsing, causing a denial of service. The panic happens before any signature is validated. This means that a compromised repository/mirror/cache can DoS clients without having access to any signing key. Version 2.3.1 fixes the issue. No known workarounds are available.