CVE-2026-39395: Cosign's verify-blob-attestation reports false positive when payload parsing fails
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: sigstore cosign 3.0.6.
Low priority for now. Upgrade to sigstore cosign 3.0.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 7, 2026
- Updated
- Jul 24, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-754
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.3
- CNA · GitHub_M
- 4.3
- 1.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sigstore | cosign | cpe:2.3:a:sigstore:cosign |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
sigstore cosign
- >= 3.0.0, < 3.0.6, < 2.6.3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sigstore cosignbefore 2.6.3
- sigstore cosign3.0.0 and later · before 3.0.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.23 | cosign | from 3.0.0 · before 2.6.3-r0 | 2.6.3-r0 |
| Alpine:v3.24 | cosign | from 3.0.0 · before 3.0.6-r0 | 3.0.6-r0 |
| Debian:13 | cosign | from 0 | — |
| Debian:14 | cosign | before 2.6.3-1 | 2.6.3-1 |
| Go | github.com/sigstore/cosign | from 0 | — |
| Go | github.com/sigstore/cosign | up to and including 1.13.6 | — |
| Go | github.com/sigstore/cosign/v2 | before 2.6.3 | 2.6.3 |
| Go | github.com/sigstore/cosign/v3 | from 3.0.0 · before 3.0.6 | 3.0.6 |
| openSUSE:Leap 16.0 | cosign | before 3.0.6-160000.1.1 | 3.0.6-160000.1.1 |
| openSUSE:Tumbleweed | cosign | before 3.0.6-1.1 | 3.0.6-1.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | cosign | before 3.0.6-150400.3.42.1 | 3.0.6-150400.3.42.1 |
| SUSE:Linux Enterprise Server 16.0 | cosign | before 3.0.6-160000.1.1 | 3.0.6-160000.1.1 |
Same product
sigstore: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-35929False positive signature verification in cosign39Monitor
- CVE-2024-29903Cosign vulnerable to machine-wide denial of service via malicious artifacts30Monitor
- CVE-2024-29902Cosign vulnerable to system-wide denial of service via malicious attachments23Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-46737Nov 7, 2023 · Possible endless data attack from attacker-controlled registry in cosign21Monitor
- ← EarlierCVE-2026-22703Jan 10, 2026 · Cosign verification accepts any valid Rekor entry under certain conditions22Monitor
- ← EarlierCVE-2026-24122Feb 19, 2026 · Cosign Certificate Chain Expiry Validation Issue Allows Issuing Certificate Expiry to Be Overlooked14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| sigstore cosign | 3.0.6 · description | Vendor (CNA) |
| alpine:cosign | 2.6.3-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:cosign | 2.6.3-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/sigstore/cosign/v2 | 2.6.3 | Package registry (OSV) |
| Go:github.com/sigstore/cosign/v3 | 3.0.6 | Package registry (OSV) |
| opensuse:cosign | 3.0.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:cosign | 3.0.6-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.