CVE-2026-54787

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

Published Jul 31, 2026 CVSS 3.1 · 3.1 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in sigstore-go originates from a missing check that compares the bundle signing timestamp against the validity window of an ExpiringKey. An attacker who possesses expired key material can use it to sign bundles that the library will accept as valid, thereby allowing tampered or malicious artifacts to be authenticated as legitimate. This bypass of signature validity compromises the integrity and authenticity of any system that relies on sigstore-go for verifying signed artifacts.

Affected Systems

The affected product is sigstore-go, a Go library for Sigstore signing and verification, provided by sigstore. All versions prior to 1.2.1 are vulnerable. The flaw was addressed in release 1.2.1.

Risk and Exploitability

CVSS score of 3.1 indicates low severity, and the EPSS score of less than 1% suggests a very low probability of exploitation. It is not listed in the CISA KEV catalog. The flaw could be exploited when an attacker supplies malicious bundles to a system using sigstore-go, because the library will accept them without verifying key lifetime. Successful exploitation would enable an attacker to introduce compromised artifacts into the build or deployment pipeline. The likely attack vector is the supply chain where an attacker injects signed bundles into clients that use sigstore-go for verification.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade sigstore-go to v1.2.1
  • Restrict the use of ExpiringKey instances that have expired timestamps and enforce timestamp validation during verification
  • If an upgrade is not possible, revoke or replace any expired key material and prevent the use of unverified bundles

Generated by OpenCVE AI on August 4, 2026 at 22:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-wqqc-jjcq-vfxm sigstore-go fails to check signature timestamps against a signing key's validity period
History
Type Values Removed Values Added
First Time appeared Redhat
Redhat hummingbird
Weaknesses CWE-347
CPEs cpe:/a:redhat:hummingbird:1
Vendors & Products Redhat
Redhat hummingbird
References
Metrics threat_severity

None

threat_severity

Low

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Sigstore
Sigstore sigstore-go
Vendors & Products Sigstore
Sigstore sigstore-go
Type Values Removed Values Added
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.
Title sigstore-go fails to check signature timestamps against a signing key's validity period
Weaknesses CWE-324
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-324

    Use of a Key Past its Expiration Date

  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 31, 2026, 11:36 PM
Reserved
Jun 15, 2026, 11:23 PM
Status
Awaiting Analysis
Published
Jul 31, 2026, 11:17 PM
Modified
Oct 23, 2026, 11:10 PM
Severity
Low
Public date
Jul 31, 2026, 9:58 PM