https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T02:26:00.785434+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-161063 EUVD-2026-161063 2026-10-04T02:26:00.851479+00:00 EUVD-2026-161063 https://cve.radiocsirt.org/vuln/fkie_cve-2023-47122 fkie_cve-2023-47122 2026-10-04T02:26:00.851519+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-xvrc-2wvh-49vc GHSA-xvrc-2wvh-49vc — Gitsign's Rekor public keys fetched from upstream API instead of local TUF client. 2026-10-04T02:26:00.851554+00:00

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

 https://cve.radiocsirt.org/vuln/gsd-2023-47122 gsd-2023-47122 2026-10-04T02:26:00.851587+00:00 gsd-2023-47122