Vulnerability · Published Jul 31, 2026 · Assigned by GitHub_M

CVE-2026-54787sigstore-go fails to check signature timestamps against a signing key's validity period

Low 3.1

In plain English

A low-severity security flaw in sigstore-go from sigstore. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)3.1Low
Exploit odds (30 days)0.1%top 97.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13sigstore-gono fix listedDEBIAN-CVE-2026-54787
Debian:14sigstore-go1.2.1-1DEBIAN-CVE-2026-54787
Gogithub.com/sigstore/sigstore-go1.2.1GHSA-wqqc-jjcq-vfxm
Gogithub.com/sigstore/sigstore-go1.2.1GO-2026-6162
Ubuntu:26.10sigstore-gono fix listedUBUNTU-CVE-2026-54787

Affected products (as reported)

VendorProductVersions
sigstore sigstore-go < 1.2.1

Weakness: CWE-324 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

References