PatchSiren cyber security CVE debrief
CVE-2026-39395 Sigstore CVE debrief
CVE-2026-39395 is a vulnerability in Cosign, a code signing and transparency tool for containers and binaries. The vulnerability allows cosign verify-blob-attestation to erroneously report a 'Verified OK' result for attestations with malformed payloads or mismatched predicate types. This issue was fixed in Cosign versions 3.0.6 and 2.6.3. The vulnerability affects users of Cosign, especially those relying on verify-blob-attestation for security. It is recommended to upgrade to a fixed version and review verification processes to ensure correct predicate type validation.
- Vendor
- Sigstore
- Product
- Cosign
- CVSS
- MEDIUM 4.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-07
- Original CVE updated
- 2026-07-24
- Advisory published
- 2026-04-07
- Advisory updated
- 2026-07-24
Who should care
Users of Cosign, especially those relying on verify-blob-attestation for security, should be aware of this vulnerability and upgrade to a fixed version. This includes operators, platform administrators, vulnerability management teams, and security teams who use Cosign for code signing and transparency.
Technical summary
The vulnerability was caused by a logic flaw in the error handling of predicate type validation for old-format bundles and detached signatures, and a complete bypass of predicate type validation for new-format bundles. This could lead to incorrect verification results, potentially allowing malicious attestations to be accepted. The vulnerability is fixed in Cosign versions 3.0.6 and 2.6.3. Users should review and update verification processes to ensure correct predicate type validation and monitor for potential incorrect verification results.
Defensive priority
High
Recommended defensive actions
- Upgrade to Cosign version 3.0.6 or 2.6.3 or later
- Review and update verification processes to ensure correct predicate type validation
- Monitor for and address potential incorrect verification results
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record was published on 2026-04-07T20:16:33.140Z and last modified on 2026-07-24T21:10:00.143Z. The NVD entry is currently Analyzed. 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. The evidence for this CVE is based on the official CVE record and NVD detail page.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-39395 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-39395
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-39395 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-39395
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/sigstore/cosign/security/advisories/GHSA-w6c6-c85g-mmv6
[email protected] - Mitigation, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.