CVE-2026-54787
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…
Does this matter?
Lower severity and a low EPSS score (0.09%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 3.1 LOWCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
- EPSS
- 0.09% probability · 1th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-324
- Source
- security-advisories@github.com
References
- 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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.