GHSA-xm5m-wgh2-rrg3

Sigstore Timestamp Authority has Improper Certificate Validation in verifier in github.com/sigstore/timestamp-authority

Medium highest severity reported · also known as CVE-2026-39984, GO-2026-5763

2
catalog tools match this advisory
1
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.1%
EPSS for CVE-2026-39984, percentile 1

Catalog tools matching GHSA-xm5m-wgh2-rrg3

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
slsa-verifier
Supply Chain Compliance
v2.7.1github.com/sigstore/timestamp-authority@v1.2.2
golang
no fix listedvulnerable code in binarygo.modDispute
kube-linter
Kubernetes Security
v0.8.3github.com/sigstore/timestamp-authority/v2@v2.0.3
golang
2.0.6not in released binarytool-imports/go.modDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-xm5m-wgh2-rrg3 · NVD CVE-2026-39984 · Go vulnerability GO-2026-5763 · OSV GHSA-xm5m-wgh2-rrg3

Grype data sources: https://github.com/advisories/GHSA-xm5m-wgh2-rrg3 · https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-xm5m-wgh2-rrg3