Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-39395: CWE-754: Improper Check for Unusual or Exceptional Conditions in sigstore cosign

0
Medium
VulnerabilityCVE-2026-39395cvecve-2026-39395cwe-754
Published: Tue Apr 07 2026 (04/07/2026, 20:06:28 UTC)
Source: CVE Database V5
Vendor/Project: sigstore
Product: 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

AILast updated: 04/07/2026, 20:31:59 UTC

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses