CLEANSTART-2026-HF60121 Security fix for CVE-2026-54787 applied in: cosign 2.6.4-r2, cosign 3.1.2-r1, crossplane 2.3.4-r2, kyverno 1.16.4-r3, kyverno 1.17.2-r2, kyverno 1.18.1-r4, policy-controller-fips 0.15.1-r1, spire-server 1.14.7-r0, tekton-chains 0.25.2-r1, tekton-chains 0.26.5-r1, tekton-chains-fips 0.25.2-r1, tekton-chains-fips 0.26.5-r1, tkn 0.42.2-r1, tkn 0.43.2-r1, tkn 0.44.2-r1, tkn 0.45.0-r1

CVE-2026-54787 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details...

CVE-2026-54787 affecting package gh for versions less than 2.97.0-1

CVE-2026-54787 affecting package gh for versions less than 2.97.0-1. An upgraded version of the package is available that resolves this issue...

CLEANSTART-2026-RN13668 Security fixes in cosign 2.6.4-r2

Package cosign version 2.6.4-r2 fixes 2 vulnerabilities: CVE-2026-54787, ghsa-hrxh-6v49-42gf...

CLEANSTART-2026-SK52724 Security fixes in cosign 3.1.2-r1

Package cosign version 3.1.2-r1 fixes 9 vulnerabilities: CVE-2026-54787, ghsa-hrxh-6v49-42gf, ghsa-259r-337f-4rfw, CVE-2026-49835, ghsa-9c54-x2g4-v92j...

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

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...

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

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...

CVE-2026-54787

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...