Is github.com/sigstore/cosign 1.13 vulnerable?
Go · 7 releases from 1.13.0 to 1.13.6 · latest github.com/sigstore/cosign is 1.13.6 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. github.com/sigstore/cosign 1.13.6, the last 1.13 release, is affected by 10 known security advisories (3 medium, 7 low), including CVE-2026-39395, CVE-2024-29903, CVE-2024-29902. 1 more affects earlier 1.13.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/sigstore/cosign?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/sigstore/cosign 1.13.6
Cosign's verify-blob-attestation reports false positive when payload parsing fails in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign's verify-blob-attestation reports false positive when payload parsing fails
- Affected
- <=1.13.6
- Fixed in
- No fix released
Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped
- Affected
- <3.0.5
- Fixed in
- 3.0.5
Cosign verification accepts any valid Rekor entry under certain conditions in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign malicious attachments can cause system-wide denial of service in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign malicious artifacts can cause machine-wide DoS
- Affected
- <=2.2.3
- Fixed in
- No fix released
Cosign malicious attachments can cause system-wide denial of service
- Affected
- <=2.2.3
- Fixed in
- No fix released
Denial of service attack from remote registry in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Fixed within 1.13.x, affecting earlier releases
Cosign vulnerable to possible endless data attack from attacker-controlled registry
- Affected
- <1.13.2
- Fixed in
- 1.13.2
Every github.com/sigstore/cosign 1.13.x release
Affected: 1.13.0 to 1.13.6.
| Version | Known advisories |
|---|---|
| github.com/sigstore/cosign 1.13.6 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737 |
| github.com/sigstore/cosign 1.13.5 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737 |
| github.com/sigstore/cosign 1.13.4 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737 |
| github.com/sigstore/cosign 1.13.3 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737 |
| github.com/sigstore/cosign 1.13.2 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737 |
| github.com/sigstore/cosign 1.13.1 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737, CVE-2023-46737 |
| github.com/sigstore/cosign 1.13.0 | CVE-2026-39395, CVE-2026-39395, CVE-2026-24122, CVE-2026-24122, CVE-2026-22703, CVE-2024-29902, CVE-2024-29903, CVE-2024-29903, CVE-2024-29902, CVE-2023-46737, CVE-2023-46737 |
Which of your client projects are still on github.com/sigstore/cosign 1.13?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/sigstore/cosign version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/sigstore/cosign versions
- github.com/sigstore/cosign 1.12
- github.com/sigstore/cosign 1.11
- github.com/sigstore/cosign 1.10
- github.com/sigstore/cosign 1.9
- github.com/sigstore/cosign 1.8
- github.com/sigstore/cosign 0.6
- github.com/sigstore/cosign 0.5
- github.com/sigstore/cosign 0.4
- github.com/sigstore/cosign 0.3
- github.com/sigstore/cosign 0.2
- github.com/sigstore/cosign 0.1
- All github.com/sigstore/cosign advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.