Read the docs
TI-2022-16356 Aliases CVE-2022-35929GHSA-vjxv-45g9-9296

False positive signature verification in cosign

Priority HIGH 76CWE-347Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 3 without a fix

Attack profile from CVSS 3.1 · NVD. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-347.

Summary

cosign is a container signing and verification utility. In versions prior to 1.10.1 cosign can report a false positive if any attestation exists. `cosign verify-attestation` used with the `--type` flag will report a false positive verification when there is at least one attestation with a valid signature and there are NO attestations of the type being verified (--type defaults to "custom"). This can happen when signing with a standard keypair and with "keyless" signing with Fulcio. This vulnerability can be reproduced with the `distroless.dev/static@sha256:dd7614b5a12bc4d617b223c588b4e0c833402b8f4991fb5702ea83afad1986e2` image. This image has a `vuln` attestation but not an `spdx` attestation. However, if you run `cosign verify-attestation --type=spdx` on this image, it incorrectly succeeds. This issue has been addressed in version 1.10.1 of cosign. Users are advised to upgrade. There are no known workarounds for this issue.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00684 52nd percentileScored 2026-11-07
Public exploit Yes 2 exploit referencesTagged by NVD
Fix Partial cosign (sigstore): 1.10.1github.com/sigstore/cosign (Go): 1.10.1Red Hat: 3 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
sigstorecosignbefore 1.10.11.10.1Patch availableCNA
—github.com/sigstore/cosign (Go)before 1.10.11.10.1Patch availableGHSA-vjxv-45g9-9296
  • cosign Vendorsigstore Affected before 1.10.1 Fixed in 1.10.1 Patch available CNA
  • github.com/sigstore/cosign (Go) Vendor— Affected before 1.10.1 Fixed in 1.10.1 Patch available GHSA-vjxv-45g9-9296

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*before 1.10.1Vulnerablesigstore
  • cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:* Versions before 1.10.1 Vulnerable ·sigstore

Remediation

  • Fix · CNA cosign (sigstore) Fixed in 1.10.1
  • Fix · GHSA-vjxv-45g9-9296 github.com/sigstore/cosign (Go) Fixed in 1.10.1 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
OpenShift ServerlessAffectedNo fix planned: Will not fix
Red Hat Advanced Cluster Security 3AffectedNo fix planned: Will not fix
Red Hat OpenShift Container Platform 4AffectedNo fix yet: Fix deferred

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-35929
  2. 2026-10-03 Alias added: GHSA-vjxv-45g9-9296
  3. 2026-10-04 EPSS moved to the 50th–90th percentile

References

Exploit 2

Advisory 1

Other 1

  • TI-2024-19670 Cosign vulnerable to machine-wide denial of service via malicious artifacts CVSS 3.1HIGH 7.5
  • TI-2024-19669 Cosign vulnerable to system-wide denial of service via malicious attachments CVSS 3.1MEDIUM 5.9
  • TI-2022-16479 Vulnerabilities with blob verification in sigstore cosign CVSS 3.1MEDIUM 5.5
  • TI-2023-25220 Possible endless data attack from attacker-controlled registry in cosign CVSS 3.1MEDIUM 5.3
  • TI-2026-28380 Cosign's verify-blob-attestation reports false positive when payload parsing fails CVSS 3.1MEDIUM 5.3
  • TI-2026-18230 Cosign verification accepts any valid Rekor entry under certain conditions CVSS 3.1MEDIUM 5.5
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences