Use of a Key Past its Expiration Date Affecting zarf package, versions <0.82.0-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.09% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-ZARF-18505817
  • published2 Aug 2026
  • disclosed31 Jul 2026

Introduced: 31 Jul 2026

NewCVE-2026-54787  (opens in a new tab)
CWE-324  (opens in a new tab)

How to fix?

Upgrade Chainguard zarf to version 0.82.0-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream zarf package and not the zarf package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1