Insufficient Verification of Data Authenticity Affecting cosign package, versions <3.0.4-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0% (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-MINIMOSLATEST-COSIGN-14954767
  • published15 Jan 2026
  • disclosed10 Jan 2026

Introduced: 10 Jan 2026

NewCVE-2026-22703  (opens in a new tab)
CWE-345  (opens in a new tab)

How to fix?

Upgrade Minimos:latest cosign to version 3.0.4-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cosign package and not the cosign package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.

CVSS Base Scores

version 3.1