# github.com/sigstore/cosign/v2 (Go) vulnerabilities

6 known vulnerabilities (4 medium, 2 low), with the versions each affects and the releases that fix them.

## At a glance

- Latest release: not known (cve.now hasn't read this package's releases)
- Newest unaffected release: not known without release data
- Registry: https://pkg.go.dev/github.com/sigstore/cosign/v2

## Advisories (6)

### [CVE-2026-39395](https://cve.now/CVE-2026-39395): Cosign's verify-blob-attestation reports false positive when payload parsing fails

- Severity: Medium 4.3
- Published: Apr 7, 2026
- Affected: fixed in 2.6.3.

### [CVE-2026-24122](https://cve.now/CVE-2026-24122): Cosign Certificate Chain Expiry Validation Issue Allows Issuing Certificate Expiry to Be Overlooked

- Severity: Low 3.7
- Published: Feb 19, 2026
- Affected: all versions.

### [CVE-2026-22703](https://cve.now/CVE-2026-22703): Cosign verification accepts any valid Rekor entry under certain conditions

- Severity: Medium 5.5
- Published: Jan 10, 2026
- Affected: fixed in 2.6.2.

### [CVE-2024-29903](https://cve.now/CVE-2024-29903): Cosign vulnerable to machine-wide denial of service via malicious artifacts

- Severity: Medium 4.2
- Published: Apr 10, 2024
- Affected: fixed in 2.2.4.

### [CVE-2024-29902](https://cve.now/CVE-2024-29902): Cosign vulnerable to system-wide denial of service via malicious attachments

- Severity: Medium 4.2
- Published: Apr 10, 2024
- Affected: fixed in 2.2.4.

### [CVE-2023-46737](https://cve.now/CVE-2023-46737): Possible endless data attack from attacker-controlled registry in cosign

- Severity: Low 3.1
- Published: Nov 7, 2023
- Affected: fixed in 2.2.1.

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/packages/go/github.com/sigstore/cosign/v2
Site guide for agents: https://cve.now/llms.txt
Uses NVD data; not endorsed by NVD.