CVE-2026-39984: Sigstore Timestamp Authority has Improper Certificate Validation in verifier

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-04-15 · updated 2026-10-26
Weakness: CWE-295

Description

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Affected products

sigstore timestamp-authority: before 2.0.6 — fixed in 2.0.6

How to fix

Upgrade to a fixed version: sigstore timestamp-authority 2.0.6. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-39984 or the next vulnerability affects your stack