CVE-2026-39395: Cosign's verify-blob-attestation reports false positive when payload parsing fails

Published Apr 7, 2026
·
Updated

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.

Other sources

Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, 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. This vulnerability is fixed in 3.0.6 and 2.6.3.

MITRE

Affected Software

4 affected componentsFixes available
go/github.com/sigstore/cosign<2.6.3
2.6.3
go/github.com/sigstore/cosign>=3.0.0<3.0.6
3.0.6
sigstore Cosign<2.6.3
sigstore Cosign>=3.0.0<3.0.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/sigstore/cosign to a version that resolves this vulnerability.

    Fixed in 2.6.3
  2. Upgrade

    Upgrade go/github.com/sigstore/cosign to a version that resolves this vulnerability.

    Fixed in 3.0.6
  3. Upgrade

    Upgrade cosign to a version that resolves this vulnerability.

    Fixed in 3.0.6
  4. Upgrade

    Upgrade cosign to a version that resolves this vulnerability.

    Fixed in 2.6.3
  5. Configuration

    Always set --check-claims=true for attestation verification.

    cosign verify-blob-attestation --check-claims = true

Event History

Apr 7, 2026
CVE Published
via MITRE·08:06 PM
Data Sourced
via MITRE·08:06 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
Affected Software
Apr 8, 2026
Advisory Published
via GitHub·12:15 AM
Data Sourced
via GitHub·12:15 AM
DescriptionSeverityWeaknessAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203