CVE-2026-22703CWE-345

Cosign verification accepts any valid Rekor entry under certain conditions

Medium · published January 10, 2026

CVSS v3.1
5.5
EPSS
0%
Percentile
1.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
5.5 · MEDIUM
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00106 · 1.1th percentile
Weakness
CWE-345 · Insufficient Verification of Data Authenticity
Published
2026-01-10T06:11Z
EPSS history
Timeline
  • 10 JAN 06:11Z
    Cosign verification accepts any valid Rekor entry under certain conditions
    cvelistv5