GitHub Advisoryadvisory · Go
GHSA-w6c6-c85g-mmv6 Cosign's verify-blob-attestation reports false positive when payload parsing fails
MEDIUM
Official page ↗
- Aliases
- CVE-2026-39395
- Ecosystem
- Go
- Packages
- github.com/sigstore/cosign
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-754
- Reviewed
- 2026-04-08
Affected packages
• Go github.com/sigstore/cosign: >= 3.0.0, < 3.0.6 → fixed in 3.0.6
• Go github.com/sigstore/cosign: < 2.6.3 → fixed in 2.6.3
Description
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 ` 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.
Related
Alias · CVE (1)
- CVE-2026-39395 Cosign provides code signing and transparency for containers and binaries. vulnerability
Weakness · CWE (1)
- CWE-754 Improper Check for Unusual or Exceptional Conditions weakness