cve.bz

CVE-2026-39984 linuxfoundation sigstore timestamp authority: Improper Certificate Validation

5.5 mediumEPSS 0.1%Fix available

Medium (5.5) in linuxfoundation sigstore timestamp authority. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/sigstore/timestamp-authority/v2 2.0.6.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-39984 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-39984?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-39984?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-39984 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:sigstore_timestamp_authoritybefore 2.0.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xm5m-wgh2-rrg3Gogithub.com/sigstore/timestamp-authority/v2<2.0.62.0.6
GO-2026-5763Gogithub.com/sigstore/timestamp-authorityall versionsno fix published
GO-2026-5763Gogithub.com/sigstore/timestamp-authority/v2<2.0.62.0.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13golang-github-sigstore-timestamp-authorityno fix listedDEBIAN-CVE-2026-39984
Debian14golang-github-sigstore-timestamp-authority2.1.0-1DEBIAN-CVE-2026-39984
Ubuntu25.10, 26.04:LTS, 26.10golang-github-sigstore-timestamp-authorityno fix listedUBUNTU-CVE-2026-39984
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 12 moredocker29.4.0_ce-150000.253.1SUSE-SU-2026:2692-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0docker29.4.0_ce-160000.7.1SUSE-SU-2026:22367-1
SUSELinux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1docker29.7.2_ce-160100.3.1SUSE-SU-2026:24740-1
SUSELinux Micro 6.0docker29.4.0_ce-11.1SUSE-SU-2026:22513-1
SUSELinux Micro 6.0docker29.7.2_ce-159998.1.1SUSE-SU-2026:24318-1
SUSELinux Micro 6.1docker29.4.0_ce-slfo.1.1_10.1SUSE-SU-2026:22456-1
SUSELinux Micro 6.1docker29.7.2_ce-slfo.1.1_11.1SUSE-SU-2026:24279-1
SUSELinux Micro 6.2docker29.4.0_ce-160000.7.1SUSE-SU-2026:22285-1
SUSELinux Micro 6.2docker29.7.2_ce-160000.8.1SUSE-SU-2026:24410-1
openSUSELeap 16.0docker29.4.0_ce-160000.7.1openSUSE-SU-2026:21060-1
openSUSELeap 16.0docker29.7.2_ce-160000.8.1openSUSE-SU-2026:22158-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSELeap 16.1docker29.7.2_ce-160100.3.1openSUSE-SU-2026:22345-1
openSUSETumbleweeddocker29.4.0_ce-40.1openSUSE-SU-2026:11144-1
openSUSETumbleweedhauler1.4.3-1.1openSUSE-SU-2026:10702-1
openSUSETumbleweedtrivy0.70.0-1.1openSUSE-SU-2026:10651-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability allows an attacker to bypass authorization checks by prepending a forged certificate to the certificate bag. The library validates the signature against one certificate while performing authorization checks against another.

Additionally, a user or an automated system must actively run the `VerifyTimestampResponse` function against the attacker-supplied payload. Due to this reason, this flaw has been rated with a moderate severity.

This issue only impacts users of the `timestamp-authority/v2/pkg/verification` package and does not affect the `timestamp-authority` service or `sigstore-go`.

Red Hat's mitigation

To mitigate this vulnerability, users of VerifyTimestampResponse can use the TSACertificate option to explicitly specify the exact certificate they expect to be used.

ProductPackageStateAdvisory
Red Hat Advanced Cluster Security 4advanced-cluster-security/rhacs-main-rhel8Fix deferred
Red Hat Advanced Cluster Security 4advanced-cluster-security/rhacs-rhel8-operatorFix deferred
Red Hat Advanced Cluster Security 4advanced-cluster-security/rhacs-roxctl-rhel8Fix deferred
Red Hat Advanced Cluster Security 4advanced-cluster-security/rhacs-scanner-v4-rhel8Fix deferred
Red Hat Trusted Artifact Signerrhtas/cosign-rhel9Fix deferred
Red Hat Trusted Artifact Signerrhtas/ec-rhel9Fix deferred
Red Hat Trusted Artifact Signerrhtas/gitsign-rhel9Fix deferred
Security Profiles Operatorcompliance/openshift-security-profiles-operator-bundleFix deferred
Security Profiles Operatorcompliance/openshift-security-profiles-rhel8-operatorFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-39984.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON