CVE-2026-39395: CWE-754: Improper Check for Unusual or Exceptional Conditions in sigstore cosign
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.
AI Analysis
Technical Summary
CVE-2026-39395 affects the sigstore cosign tool used for code signing and transparency of containers and binaries. In versions >= 3.0.0 and < 3.0.6, and versions < 2.6.3, the verify-blob-attestation command may incorrectly validate attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was caused by a logic flaw in error handling during predicate type validation. For new-format bundles, predicate type validation was completely bypassed. This vulnerability allows erroneous verification results, potentially undermining trust in signed artifacts. The issue is resolved in cosign versions 3.0.6 and 2.6.3.
Potential Impact
The vulnerability can cause cosign to incorrectly report that an attestation is verified when it contains malformed or mismatched predicate data. This could lead to a false sense of security in the integrity and authenticity of signed containers or binaries. However, there is no direct impact on confidentiality or availability, and no known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade cosign to version 3.0.6 or later, or 2.6.3 or later, where this vulnerability is fixed. Patch status is confirmed by the version information in the description. No other mitigation steps are indicated.
CVE-2026-39395: CWE-754: Improper Check for Unusual or Exceptional Conditions in sigstore cosign
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-39395 affects the sigstore cosign tool used for code signing and transparency of containers and binaries. In versions >= 3.0.0 and < 3.0.6, and versions < 2.6.3, the verify-blob-attestation command may incorrectly validate attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was caused by a logic flaw in error handling during predicate type validation. For new-format bundles, predicate type validation was completely bypassed. This vulnerability allows erroneous verification results, potentially undermining trust in signed artifacts. The issue is resolved in cosign versions 3.0.6 and 2.6.3.
Potential Impact
The vulnerability can cause cosign to incorrectly report that an attestation is verified when it contains malformed or mismatched predicate data. This could lead to a false sense of security in the integrity and authenticity of signed containers or binaries. However, there is no direct impact on confidentiality or availability, and no known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade cosign to version 3.0.6 or later, or 2.6.3 or later, where this vulnerability is fixed. Patch status is confirmed by the version information in the description. No other mitigation steps are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-06T22:06:40.516Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d5660baaed68159a5b407a
Added to database: 4/7/2026, 8:16:11 PM
Last enriched: 4/7/2026, 8:31:59 PM
Last updated: 4/7/2026, 11:03:01 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.