CVE-2026-39395: 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.
Published Apr 8, 2026 · Updated Nov 12, 2026
Affected packages
github.com/sigstore/cosign/v3
- Ecosystem
- Go
- Affected
- >= 3.0.0, < 3.0.6
- Fixed in
- 3.0.6
- Check
go list -m github.com/sigstore/cosign/v3
github.com/sigstore/cosign/v2
- Ecosystem
- Go
- Affected
- < 2.6.3
- Fixed in
- 2.6.3
- Check
go list -m github.com/sigstore/cosign/v2
github.com/sigstore/cosign
- Ecosystem
- Go
- Affected
- <= 1.13.6
- Fixed in
- No patched version yet
- Check
go list -m github.com/sigstore/cosign
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to kodareef5, jamesconwaydev.
References
- https://github.com/sigstore/cosign/security/advisories/GHSA-w6c6-c85g-mmv6
- https://nvd.nist.gov/vuln/detail/CVE-2026-39395
- https://github.com/sigstore/cosign/pull/4801
- https://github.com/sigstore/cosign/commit/f1ad3ee952313be5d74a49d67ba0aa8d0d5e351f
- https://github.com/sigstore/cosign/releases/tag/v2.6.3
- https://github.com/sigstore/cosign/releases/tag/v3.0.6
- https://github.com/advisories/GHSA-w6c6-c85g-mmv6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-24122
Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped
low3.7Feb 19, 2026CVE-2026-22703
Cosign verification accepts any valid Rekor entry under certain conditions
medium5.5Jan 13, 2026CVE-2024-29902
Cosign malicious attachments can cause system-wide denial of service
medium4.2No fixApr 11, 2024CVE-2024-29903
Cosign malicious artifacts can cause machine-wide DoS
medium4.2No fixApr 11, 2024
