https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 12:56:23 +0000 https://cve.radiocsirt.org/vuln/bit-cosign-2022-35929 <p><strong>Affected:</strong> Bitnami: cosign</p> <p>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 &#34;custom&#34;). This can happen when signing with a standard keypair and with &#34;keyless&#34; 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.</p> <p><strong>Affected:</strong> Bitnami: cosign</p> <p>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 &#34;custom&#34;). This can happen when signing with a standard keypair and with &#34;keyless&#34; 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.</p> https://cve.radiocsirt.org/vuln/bit-cosign-2022-35929 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0622 certfr-2025-avi-0622 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0622 https://cve.radiocsirt.org/vuln/cleanstart-2026-eh64058 <p><strong>Affected:</strong> CleanStart: cosign</p> <p>Security vulnerability affects the cosign package. This issue is resolved in later releases. See references for vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: cosign</p> <p>Security vulnerability affects the cosign package. This issue is resolved in later releases. See references for vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-eh64058 https://cve.radiocsirt.org/vuln/euvd-2026-232656 EUVD-2026-232656 https://cve.radiocsirt.org/vuln/euvd-2026-232656 https://cve.radiocsirt.org/vuln/fkie_cve-2022-35929 <p>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 &#34;custom&#34;). This can happen when signing with a standard keypair and with &#34;keyless&#34; 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.</p> <p>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 &#34;custom&#34;). This can happen when signing with a standard keypair and with &#34;keyless&#34; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-35929 https://cve.radiocsirt.org/vuln/ghsa-vjxv-45g9-9296 <p><strong>Affected:</strong> Go: github.com/sigstore/cosign</p> <p>`cosign verify-attestation` used with the `--type` flag will report a false positive verification when:</p> <p>- There is at least one attestation with a valid signature - There are NO attestations of the type being verified (--type defaults to &#34;custom&#34;)</p> <p>This can happen when signing with a standard keypair and with &#34;keyless&#34; signing with Fulcio. Users should upgrade to cosign version 1.10.1 or greater for a patch. Currently the only workaround is to upgrade.</p> <p><strong>Affected:</strong> Go: github.com/sigstore/cosign</p> <p>`cosign verify-attestation` used with the `--type` flag will report a false positive verification when:</p> <p>- There is at least one attestation with a valid signature - There are NO attestations of the type being verified (--type defaults to &#34;custom&#34;)</p> <p>This can happen when signing with a standard keypair and with &#34;keyless&#34; signing with Fulcio. Users should upgrade to cosign version 1.10.1 or greater for a patch. Currently the only workaround is to upgrade.</p> https://cve.radiocsirt.org/vuln/ghsa-vjxv-45g9-9296 https://cve.radiocsirt.org/vuln/gsd-2022-35929 gsd-2022-35929 https://cve.radiocsirt.org/vuln/gsd-2022-35929 https://cve.radiocsirt.org/vuln/opensuse-su-2024:12240-1 <p>cosign-1.10.1-1.1 on GA media</p> <p>cosign-1.10.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:12240-1