Advisory record · GHSA-xm5m-wgh2-rrg3

Sigstore Timestamp Authority has Improper Certificate Validation in verifier

CVSS 5.5 MediumEPSS 0.0010 · 1st percentile

Published by the GitHub Advisory Database at 14 Apr 2026, 01:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/sigstore/timestamp-authority/v2Go<2.0.62.0.6
Identifiers
GHSA-xm5m-wgh2-rrg3 · CVE-2026-39984 · GO-2026-5763
Weakness (CWE)
CWE-295
Published
14 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Sigstore Timestamp Authority (github.com/sigstore/timestamp-authority/v2) versions before 2.0.6 are affected by improper certificate validation in its verification package. An attacker who can supply a timestamp response can prepend a forged certificate to the certificate bag while signing with an authorized key, which can bypass some authorization checks. Users should upgrade to version 2.0.6. Callers of VerifyTimestampResponse can instead pass the TSACertificate option to pin the expected certificate. The timestamp service itself is not affected.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0010, the 1st percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.