github.com/sigstore/cosign/v2 vulnerabilities
- Registry
- Go
- Latest
- 2.6.5
11 known advisories
The latest version, 2.6.5, is affected by 1 of them.
Is your project on an affected github.com/sigstore/cosign/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/sigstore/cosign/v2
Cosign's verify-blob-attestation reports false positive when payload parsing fails in github.com/sigstore/cosign
- Affected
- <2.6.3
- Fixed in
- 2.6.3
Cosign's verify-blob-attestation reports false positive when payload parsing fails
- Affected
- <2.6.3
- Fixed in
- 2.6.3
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 verification accepts any valid Rekor entry under certain conditions in github.com/sigstore/cosign
- Affected
- <2.6.2
- Fixed in
- 2.6.2
Cosign verification accepts any valid Rekor entry under certain conditions
- Affected
- <2.6.2
- Fixed in
- 2.6.2
Cosign malicious attachments can cause system-wide denial of service in github.com/sigstore/cosign
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Cosign malicious artifacts can cause machine-wide DoS
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Cosign malicious attachments can cause system-wide denial of service
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Denial of service attack from remote registry in github.com/sigstore/cosign
- Affected
- <2.2.1
- Fixed in
- 2.2.1
Cosign vulnerable to possible endless data attack from attacker-controlled registry
- Affected
- <2.2.1
- Fixed in
- 2.2.1
Is your github.com/sigstore/cosign/v2 version vulnerable?
- github.com/sigstore/cosign/v2 2.61 advisory in 2.6.5
- github.com/sigstore/cosign/v2 2.55 advisories in 2.5.3
- github.com/sigstore/cosign/v2 2.45 advisories in 2.4.3
- github.com/sigstore/cosign/v2 2.35 advisories in 2.3.0
- github.com/sigstore/cosign/v2 2.25 advisories in 2.2.4
- github.com/sigstore/cosign/v2 2.111 advisories in 2.1.1
Which of your client projects still run an old github.com/sigstore/cosign/v2?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.