BIT-cosign-2026-22703

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/cosign/BIT-cosign-2026-22703.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-cosign-2026-22703
Aliases
Published
2026-01-13T08:37:37.120Z
Modified
2026-01-13T09:26:12.903847Z
Summary
Cosign verification accepts any valid Rekor entry under certain conditions
Details

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.

Database specific
{
    "severity": "Medium",
    "cpes": [
        "cpe:2.3:a:sigstore:cosign:*:*:*:*:*:go:*:*"
    ]
}
References

Affected packages

Bitnami / cosign

Package

Name
cosign
Purl
pkg:bitnami/cosign

Severity

  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.2
Introduced
3.0.0
Fixed
3.0.4

Database specific

source

"https://github.com/bitnami/vulndb/tree/main/data/cosign/BIT-cosign-2026-22703.json"