Improper Verification of Cryptographic Signature Affecting cosign-fips package, versions <3.0.4-r3


Severity

Recommended
0.0
high
0
10

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

Threat Intelligence

EPSS
0.01% (1st 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-COSIGNFIPS-15235997
  • published6 Feb 2026
  • disclosed22 Jan 2026

Introduced: 22 Jan 2026

CVE-2026-23992  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade Chainguard cosign-fips to version 3.0.4-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cosign-fips package and not the cosign-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.

CVSS Base Scores

version 3.1