CVE-2026-22703 PUBLISHED

Cosign verification accepts any valid Rekor entry under certain conditions

Assigner: GitHub_M
Reserved: 08.01.2026 Published: 10.01.2026 Updated: 12.01.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS Score: 5.5

Product Status

Vendor sigstore
Product cosign
Versions
  • Version < 3.0.4 is affected
  • Version < 2.6.2 is affected

References

Problem Types

  • CWE-345: Insufficient Verification of Data Authenticity CWE