CVE-2026-547873.1LowCWE-324

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

sigstore · sigstore-go

Affected: sigstore-go · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.1%probability of exploitation in the next 30 days

2nd percentile

050100

Higher than 2% of scored CVEs

3.1LowCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

sigstore · sigstore-go< 1.2.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of a Key Past its Expiration Date · Cryptography
Vendor: sigstore
Published: July 2026
Band: Unlikely (under 1%), July 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-54787 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.