Skip to main content

Cosign EUVDEUVD-2026-19919

| CVE-2026-39395 MEDIUM
Improper Check for Unusual or Exceptional Conditions (CWE-754)
2026-04-07 GitHub_M GHSA-w6c6-c85g-mmv6
5.3
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Unusual condition handling
Impact

Despite a moderate CVSS score of 4.3 (low integrity impact, no confidentiality/availability impact, unauthenticated, low complexity), this vulnerability poses significant real-world risk in supply chain and software verification contexts. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) indicates remote, unauthenticated exploitation requiring user interaction (reviewing and acting on false verification results). The core risk is not system compromise but trust degradation: a developer or CI/CD system relying on cosign's verification output could accept malicious or tampered attestations, leading to downstream acceptance of compromised artifacts. The logic flaw in predicate validation represents a fundamental trust mechanism failure rather than a minor integrity issue. No public exploit code or CISA KEV status was identified in the provided data, but the vulnerability directly undermines the assurance properties that cosign is designed to provide, making it a priority for organizations using attestation-based supply chain verification.

Exploit ScenarioDerived

An attacker crafts a malformed attestation with an incorrect predicate type or invalid payload and submits it alongside a signed container image to a supply chain verification system or developer workstation running vulnerable Cosign. The developer or CI/CD pipeline runs cosign verify-blob-attestation on the malicious attestation, which incorrectly reports 'Verified OK' instead of rejecting the invalid predicate. The attacker's container or binary is then accepted into the trusted artifact pipeline, potentially distributing compromised code to downstream consumers who rely on the attestation verification.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 07, 2026

Cosign verify-blob-attestation incorrectly validates attestation signatures and predicate types in versions before 3.0.6 and 2.6.3, allowing remote attackers to bypass integrity verification by submitting malformed attestations or mismatched predicate types that are falsely reported as verified. The vulnerability affects container and binary code signing workflows where attestation integrity is critical for supply chain security.

RemediationAI

Vendor-released patch: Update to Cosign 3.0.6 (for 3.x users) or 2.6.3 (for 2.x users). Both versions restore proper predicate type validation for old-format bundles, detached signatures, and new-format bundles. Users should prioritize upgrading to the latest stable release in their current branch. Consult the official GitHub advisory at https://github.com/sigstore/cosign/security/advisories/GHSA-w6c6-c85g-mmv6 for detailed upgrade instructions and version compatibility notes. Until patched, organizations should manually review and audit attestations used in critical supply chain decisions.

Affected VersionsENISA

cosign < 2.6.3
cosign 3.0.0, < 3.0.6

Affected Packages

go github.com/sigstore/cosign fix: 2.6.3, 3.0.6
go github.com/sigstore/cosign/v2 fix: 2.6.3
go github.com/sigstore/cosign/v3 fix: 3.0.6
euvd cosign fix: 2.6.3, 3.0.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Cosign is a code signing and transparency tool for containers and binaries built on the Sigstore infrastructure. The vulnerability resides in the verify-blob-attestation function, which validates that attestations meet expected schema and predicate type requirements. The root cause (CWE-754: Improper Check for Unusual or Exceptional Conditions) manifests as a logic flaw in error handling during predicate type validation for old-format bundles and detached signatures, and complete bypass of validation for new-format bundles. This allows attestations with invalid payloads or incorrect predicate types to pass verification checks when they should be rejected, undermining the cryptographic guarantees that supply chain tools depend on.

Know when Cosign gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
SUSE 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Red Hat 6.5 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

3
CVSS changed
Jul 24, 2026 - 21:22 NVD
4.3 (MEDIUM) 5.3 (MEDIUM)
Patch released
Apr 08, 2026 - 02:30 nvd
Patch available
CVE Published
Apr 07, 2026 - 20:06 nvd
MEDIUM 4.3

DescriptionNVD

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Threat Intel
1
1 source
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed
SUSE Linux Enterprise Module for Basesystem 15 SP7 Fixed
SUSE Linux Enterprise Server 15 SP7 Fixed
SUSE Linux Enterprise Server 16.1 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy