Database/Container, Kubernetes & orchestration
cosign / sigstore: Cosign can be tricked into claiming a Rekor transparency-log entry exists when it does not
CVSS 3.3CVE-2022-23649Container, Kubernetes & orchestrationcurated
Impact
Cosign can be tricked into claiming a Rekor transparency-log entry exists when it does not
Who can reach it
Malicious image with a crafted signature
What to do
Upgrade cosign in the admission and CI paths
References
Related entries
- cosign / sigstore: Attacker-controlled registry returns unbounded attestations, DoSing the verifierCVE-2023-46737 · cosign / sigstoreLow
- cosign / sigstore: `cosign verify-attestation --type` returns a false positive if any attestation existsCVE-2022-35929 · cosign / sigstoreHigh
- cosign / sigstore: Multiple verify-blob flaws cause successful verification of unsigned or wrongly-signed artifactsCVE-2022-36056 · cosign / sigstoreMedium
- cosign / sigstore: A crafted bundle verifies successfully even though the embedded Rekor entry does not referenceCVE-2026-22703 · cosign / sigstoreMedium
- cosign / sigstore: verify-blob-attestation reports "Verified OK" for malformed or mismatched payloadsCVE-2026-39395 · cosign / sigstoreMedium
- cosign / sigstore: Remote image with a malicious attachment DoSes the machine running cosignCVE-2024-29902 · cosign / sigstoreMedium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.