Use of a Key Past its Expiration Date Affecting github.com/sigstore/sigstore-go/pkg/verify package, versions <1.2.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMSIGSTORESIGSTOREGOPKGVERIFY-18508018
- published2 Aug 2026
- disclosed31 Jul 2026
- credittnytown
Introduced: 31 Jul 2026
CVE-2026-54787 (opens in a new tab)How to fix?
Upgrade github.com/sigstore/sigstore-go/pkg/verify to version 1.2.1 or higher.
Overview
Affected versions of this package are vulnerable to Use of a Key Past its Expiration Date through the public-key verification path in pkg/verify/signed_entity.go. An attacker can get a bundle signed with expired long-lived key material accepted by supplying a signed bundle whose timestamp falls outside the key’s validity window. This affects verification of self-managed public-key-signed bundles that use ExpiringKey semantics without certificates. As a result, consumers can trust signatures produced after the key expired, allowing forged or stale signatures to be verified instead of being rejected.