sigstore-go fails to check signature timestamps against a signing key's validity period — GHSA-WQQC-JJCQ-VFXM

Summary

sigstore-go fails to check signature timestamps against a signing key's validity period for self-managed long-lived keys without certificates. ## Impact To verify a bundle with a self-managed long-lived key, the key needs to be wrapped in an `ExpiringKey` type that implies expiration semantics: ```go signatureVerifier, _ := signature.LoadDefaultVerifier(publicKey) expiredKey :=…

Timeline

Published by source

2026-07-31

Risk context

• Reported severity or threat level: low.
• Review exposure for the affected product or family: go: github.com/sigstore/sigstore-go.

Product

go: github.com/sigstore/sigstore-go

What to do

General, cautious steps (verify details in the official source):

• Review exposure and plan remediation based on risk and environment.
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source
• CVE Record
• NVD

Evidence and provenance

Canonical advisory ID

GHSA-WQQC-JJCQ-VFXM

Source

GitHub

Vendor

GitHub

Published by source

2026-07-31

Last source activity

2026-07-31

Additional identifiers

CVE-2026-54787

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.