CVE-2026-22703

Medium

Description

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.

SeverityMedium
CVSS5.5
Exploit probability—
ProductSigstore Cosign
PublishedJan 10, 2026
First seenJan 10, 2026
Weakness typeCWE-345CWE-345

How to fix

Update
  • sigstore cosign2.6.2, 3.0.4 or later
  • github.com/sigstore/cosign/v33.0.4 or later
  • github.com/sigstore/cosign/v22.6.2 or later

Affected products

ProductAffected versionsFixed in
sigstore cosignv < 2.6.2, 3.0.0 ≤ v < 3.0.42.6.2, 3.0.4
github.com/sigstore/cosign/v3Gov < 3.0.43.0.4
github.com/sigstore/cosign/v2Gov < 2.6.22.6.2
github.com/sigstore/cosignGoNo range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.