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