Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
sigstore-go versions before 1.2.1 do not check a bundle's signing time against the validity window of a self-managed long-lived key wrapped in an ExpiringKey. An attacker who holds expired key material could sign bundles that verification still accepts, though the issue affects only this long-lived key workflow and not certificate-based deployments. Upgrade to sigstore-go 1.2.1 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 3.1 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0013, the 2nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-wqqc-jjcq-vfxm
- OSV: GHSA-wqqc-jjcq-vfxm
- github.com/sigstore/sigstore-go/security/advisories/GHSA-wqqc-jjcq-vfxm
- github.com/sigstore/sigstore-go/pull/642
- github.com/sigstore/sigstore-go/commit/4594ab4c779d08be1f4419803a8249188f35ed5f
- github.com/sigstore/sigstore-go
- github.com/sigstore/sigstore-go/releases/tag/v1.2.1