Advisory

GHSA-w6c6-c85g-mmv6

Also known as: BIT-cosign-2026-39395, CVE-2026-39395, GO-2026-5694

Summary

Cosign's verify-blob-attestation reports false positive when payload parsing fails

Details

Description

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.

Impact

When cosign verify-blob-attestation is used without --check-claims set to true, an attestation that has a valid signature but a malformed or unparsable payload would be incorrectly validated. Additionally, systems relying on --type <predicate type> to reject attestations with mismatched types would be lead to trust the unexpected attestation type.

Patches

v3.0.6, v2.6.3

Workarounds

Always set --check-claims=true for attestation verification.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-08 00:15 UTC
Modified
2026-11-12 18:30 UTC

Affected packages and fixes

github.com/sigstore/cosign/v3

Go · All systems

Affected

  • introduced 3.0.0, fixed 3.0.6 (semver)

Fixed versions

3.0.6

Fix

github.com/sigstore/cosign/v2

Go · All systems

Affected

  • introduced 0, fixed 2.6.3 (semver)

Fixed versions

2.6.3

Fix

github.com/sigstore/cosign

Go · All systems

Affected

  • introduced 0, last affected 1.13.6 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences