sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.1, sigstore-go does not check a bundle signing timestamp against the validity window of an ExpiringKey wrapping a self-managed long-lived signing key without a certificate, which can allow an attacker holding expired key material to sign accepted bundles. This issue is fixed in version 1.2.1.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 3.1NVD modified 2026-10-23 23:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/sigstore/sigstore-go/commit/4594ab4c779d08be1f4419803a8249188f35ed5f
- https://github.com/sigstore/sigstore-go/pull/642
- https://github.com/sigstore/sigstore-go/releases/tag/v1.2.1
- https://github.com/sigstore/sigstore-go/security/advisories/GHSA-wqqc-jjcq-vfxm
- https://github.com/sigstore/sigstore-go/security/advisories/GHSA-wqqc-jjcq-vfxm