CVE-2022-35929
CVE-2022-35929 is a high-severity vulnerability in Sigstore Cosign with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-347.
Key facts
- Severity: High (CVSS 3.x base score 7.1)
- EPSS exploit prediction: 1% (41st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-347
- Affected product: Sigstore Cosign
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2022-35929?
- 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.
- How severe is CVE-2022-35929?
- CVE-2022-35929 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2022-35929 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-35929?
- CVE-2022-35929 affects Sigstore Cosign. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2022-35929?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2022-35929 published?
- CVE-2022-35929 was published on 2022-08-04 and last updated on 2026-06-17.
References
- https://github.com/sigstore/cosign/commit/c5fda01a8ff33ca981f45a9f13e7fb6bd2080b94
- https://github.com/sigstore/cosign/security/advisories/GHSA-vjxv-45g9-9296
Affected products (1)
- cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*
More vulnerabilities in Sigstore Cosign
- CVE-2026-22703 — Medium (CVSS 5.5): Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign…
- CVE-2022-36056 — Medium (CVSS 5.5): Cosign is a project under the sigstore organization which aims to make signatures invisible infrastructure. In versions…
- CVE-2026-39395 — Medium (CVSS 4.3): Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, cosign…
- CVE-2024-29903 — Medium (CVSS 4.2): Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted…
- CVE-2024-29902 — Medium (CVSS 4.2): Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, a remote image with…
- CVE-2026-24122 — Low (CVSS 3.7): Cosign provides code signing and transparency for containers and binaries. In versions 3.0.4 and below, an issuing…
All CVEs affecting Sigstore Cosign →
Other CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities
- CVE-2026-48558 — Critical (CVSS 10.0): SimpleHelp versions 5.5.15 and prior and 6.0 pre-release versions contain an authentication bypass vulnerability in the…
- CVE-2023-25574 — Critical (CVSS 10.0): `jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI).…
- CVE-2024-45409 — Critical (CVSS 10.0): The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <=…
- CVE-2024-32962 — Critical (CVSS 10.0): xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default…
- CVE-2022-24884 — Critical (CVSS 10.0): ecdsautils is a tiny collection of programs used for ECDSA (keygen, sign, verify). `ecdsa_verify_[prepare_]legacy()`…
- CVE-2021-33885 — Critical (CVSS 10.0): An Insufficient Verification of Data Authenticity vulnerability in B. Braun SpaceCom2 prior to 012U000062 allows a…
Browse all CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities →