github.com/sigstore/cosign/v3
Affected
- introduced
3.0.0, fixed3.0.6(semver)
Fixed versions
3.0.6
Fix
- Fixed version
3.0.6go get github.com/sigstore/cosign/[email protected]
Advisory
Also known as: BIT-cosign-2026-39395, CVE-2026-39395, GO-2026-5694
Cosign's verify-blob-attestation reports false positive when payload parsing fails
Description
cosign verify-blob-attestation may erroneously report a "Verified OK" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely.
Impact
When cosign verify-blob-attestation is used without --check-claims set to true, an attestation that has a valid signature but a malformed or unparsable payload would be incorrectly validated. Additionally, systems relying on --type <predicate type> to reject attestations with mismatched types would be lead to trust the unexpected attestation type.
Patches
v3.0.6, v2.6.3
Workarounds
Always set --check-claims=true for attestation verification.
Medium Basis: The source's own band: MODERATE
3.0.0, fixed 3.0.6 (semver)3.0.6
3.0.6go get github.com/sigstore/cosign/[email protected]0, fixed 2.6.3 (semver)2.6.3
2.6.3go get github.com/sigstore/cosign/[email protected]0, last affected 1.13.6 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0