LowGO-2024-3252CVE-2024-51746GHSA-8pmp-678w-c8xx
gitsign may use incorrect Rekor entries during verification in github.com/sigstore/gitsign
Published 6 Nov 2024 · Updated 3 Mar 2026
Is your project on an affected github.com/sigstore/gitsign?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.11.0
- Fixed in
- 0.11.0
Update to the fixed version for your release line, for example:
go get github.com/sigstore/gitsign@v0.11.0Details
gitsign may use incorrect Rekor entries during verification in github.com/sigstore/gitsign
Is GO-2024-3252 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/sigstore/gitsign, and gives you the command that fixes it.
More advisories for github.com/sigstore/gitsign
- LowCVE-2026-44310gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers in github.com/sigstore/gitsign · 25 Jun 2026
- LowCVE-2026-44309gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits in github.com/sigstore/gitsign · 25 Jun 2026
- MediumCVE-2026-44309gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits · 8 May 2026
- MediumCVE-2026-44310gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers · 8 May 2026
- LowCVE-2023-47122Gitsign's Rekor public keys fetched from upstream API instead of local TUF client. in github.com/sigstore/gitsign · 21 Aug 2024
- MediumCVE-2023-47122Gitsign's Rekor public keys fetched from upstream API instead of local TUF client. · 14 Nov 2023
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.