CVE-2022-35929

criticalpriority · track · 39EPSS 0.007 · 52 %ileEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

0.68% (52nd) EPSS

CVSS 9.8 · critical

Is it mine?

4 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · osv · nvd

EPSS · scored 2026-10-27

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.

cvss

Technical severity, 0–10. One row per scoring source.

9.8

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.1–9.8

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hprimary · NVD / NIST USexploitability 3.9 · impact 5.9

v3.17.1highCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:Hsecondary · ENISA EU

v3.17.1highCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:Hsecondary · security-advisories@github.comexploitability 1.2 · impact 5.9

v3.17.1highCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:Hsecondary · OSV

v3.19criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: poc · Automatable: no · Technical Impact: totalcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-347USCWE-347US

affected products (4)

Products and version ranges known to be affected.

sigstore cosign≤ < 1.10.1enisa_euvdEU
sigstore cosign< 1.10.1nvdUScpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*
Bitnami cosign< 1.10.1osvUSpkg:bitnami/cosign
Go github.com/sigstore/cosign< 1.10.1osvUSpkg:golang/github.com/sigstore/cosign

advisories (3)

Vendor and ecosystem advisories describing this.

GHSA-vjxv-45g9-9296cosign's `cosign verify-attestaton --type` can report a false positive if any attestation exists2022-08-10ghsa · osvUS
`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 - 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. Users should upgrade to cosign version 1.10.1 or greater for a patch. Currently the only workaround is to upgrade.
BIT-cosign-2022-35929False positive signature verification in cosign2024-03-06vendor · osvUS
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.
GO-2022-0758Improper verification of signature attestations in github.com/sigstore/cosign2023-11-09vendor · osvUS
Improper verification of signature attestations in github.com/sigstore/cosign

also known as (6)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd osv nvd NVD CVE.org MITRE

published 2022-08-04modified 2026-06-17

references (10)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan