Bug 2458542 (CVE-2026-39984) - CVE-2026-39984 timestamp-authority/v2/pkg/verification: improper certificate validation in verifier
Summary: CVE-2026-39984 timestamp-authority/v2/pkg/verification: improper certificate ...
Keywords:
Status: NEW
Alias: CVE-2026-39984
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2458928 2458932 2458933 2458934 2458927 2458929 2458930 2458931
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-15 00:01 UTC by OSIDB Bzimport
Modified: 2026-04-30 04:17 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-04-15 00:01:40 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.