Skip to content
VulniPulse
Sign in
Advisory severityLow3.1Red Hat Linux

Low [CVE-2026-54787] Signature bypass allows acceptance of bundles signed with expired keys

This low-severity Red Hat Linux advisory covers CVE-2026-54787 affecting Red Hat Hardened Images.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-54787 Source published Source updated

VulniPulse record published Record updated

CVE-2026-54787
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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. A flaw was found in sigstore-go, a software library used for verifying digital signatures.

This vulnerability specifically affects the workflow for self-managed long-lived signing keys that do not use certificates. An attacker who possesses an expired signing key can exploit this by creating and signing software bundles that the system will incorrectly accept as valid.

This bypasses the intended security checks, potentially leading to the acceptance of unauthorized or malicious software. Red Hat severity: Low — CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N).

Weakness: CWE-347. Affected Red Hat products: Red Hat Hardened Images.

Red Hat fixing advisory: RHSA-2026:44162, RHSA-2026:44451, RHSA-2026:47889, RHSA-2026:47891.

Affected versions
  • < 1.2.1

Official advisory · high-confidence parse· fetched 26 days ago·verify at source

Fixed versions
  • 1.2.1
  • spire1-15-main-1.15.2-0.3.hum1
  • cosign-main-3.1.2-0.2.hum1
  • spire1-14-main-1.14.7-0.3.hum1
  • trivy-main-0.72.0-0.1.3.hum1
  • RHSA-2026:44162
  • RHSA-2026:44451
  • RHSA-2026:47889
  • RHSA-2026:47891

Official advisory · high-confidence parse· fetched 26 days ago·verify at source

Mitigation

Upgrade to a fixed release: 1.2.1, spire1-15-main-1.15.2-0.3.hum1, cosign-main-3.1.2-0.2.hum1, spire1-14-main-1.14.7-0.3.hum1, trivy-main-0.72.0-0.1.3.hum1, RHSA-2026:44162. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 26 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.