VYPR
← All advisories
Moderate severityOSV Advisory· Published Jan 10, 2026· Updated Jan 12, 2026

Cosign verification accepts any valid Rekor entry under certain conditions

CVE-2026-22703

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
github.com/sigstore/cosign/v3Go
< 3.0.43.0.4
github.com/sigstore/cosign/v2Go
< 2.6.22.6.2

Affected products

81

Patches

Vulnerability mechanics

References

5

News mentions

0

No linked articles in our index yet.