golang-github-sigstore-timestamp-authority: Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps
CVE-2026-39984 is fixed in 4 products on 1 platform, first by DEBIAN-CVE-2026-39984, released April 15, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| docker · opensuse-leap 16.0 | 29.7.2_ce-160000.8.1 | OPENSUSE-SU-2026:22158-1 | Nov 7, 2026 |
| docker · sles 15.6 | 29.4.0_ce-150000.253.1 | SUSE-SU-2026:2692-1 | Jun 30, 2026 |
| docker · sles 15.7 | 29.4.0_ce-150000.253.1 | SUSE-SU-2026:2692-1 | Jun 30, 2026 |
| docker · sles 16.0 | 29.4.0_ce-160000.7.1 | SUSE-SU-2026:22367-1 | Jun 25, 2026 |
| golang-github-sigstore-timestamp-authority · Debian 14 | 2.1.0-1 | DEBIAN-CVE-2026-39984 | Apr 15, 2026 |
| govulncheck-vulndb · opensuse-leap 16.0 | 0.0.20260723T184607-160000.1.1 | OPENSUSE-SU-2026:21483-1 | Jul 30, 2026 |
| nerdctl · amzn 2023 | 2.2.2-1.amzn2023.0.1 | ALAS2023-2026-1605 | Apr 27, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.