CVE-2026-54787

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

LOW
3.1
CVSS Score
Published: July 31, 2026 at 09:58 PM UTC
Updated: October 23, 2026 at 11:10 PM UTC
1 product affected across 1 vendorSigstore Go

Using sigstore-go by sigstore?

Get instant alerts when new vulnerabilities affect sigstore-go - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.1
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.2.1
Affected range stops below 1.2.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.1LOWGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-324

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card