CVE-2026-54787

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.

Severity
LOW
CVSS v3
3.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N · source cna
Exploit chance (EPSS)
0.134%
chance of exploitation in the next 30 days
higher than 2.9% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationnone
Automatableno
Technical impactpartial
Scored2026-07-31

Timeline

  1. 2026-07-31Published by the CNA21:58 UTC
  2. 2026-07-31GitHub advisory published (GHSA-wqqc-jjcq-vfxm)same day
  3. 2026-07-31CISA SSVC decision recordedsame day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-wqqc-jjcq-vfxm, affected packages:

PackageVulnerable versionsFixed in
Go github.com/sigstore/sigstore-gobefore 1.2.11.2.1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
sigstore sigstore-go

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources