Most recent entries from all

EUVD-2026-161063

fkie_cve-2023-47122

Gitsign is software for keyless Git signing using Sigstore. In versions of gitsign starting with 0.6.0 and prior to 0.8.0, Rekor public keys were fetched via the Rekor API, instead of through the local TUF client. If the upstream Rekor server happened to be compromised, gitsign clients could potentially be tricked into trusting incorrect signatures. There is no known compromise the default public good instance (`rekor.sigstore.dev`) - anyone using this instance is unaffected. This issue was fixed in v0.8.0. No known workarounds are available.

GHSA-xvrc-2wvh-49vc — Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.

Affected: Go: github.com/sigstore/gitsign

### Impact

In certain versions of gitsign, Rekor public keys were fetched via the Rekor API, instead of through the local TUF client. If the upstream Rekor server happened to be compromised, gitsign clients could potentially be tricked into trusting incorrect signatures.

There is no known compromise the default public good instance (`rekor.sigstore.dev`) - anyone using this instance is unlikely to be affected.

### Patches

This was fixed in v0.8.0 via https://github.com/sigstore/gitsign/pull/399

### Workarounds

n/a

### References _Are there any links users can visit to find out more?_

https://docs.sigstore.dev/about/threat-model/#sigstore-threat-model

Most recent entries from all

EUVD-2026-161063

fkie_cve-2023-47122

GHSA-xvrc-2wvh-49vc — Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.

gsd-2023-47122