Advisory record · GHSA-4qg8-fj49-pxjh

Sigstore Timestamp Authority allocates excessive memory during request parsing

CVSS 7.5 HighEPSS 0.0047 · 41st percentile

Published by the GitHub Advisory Database at 5 Dec 2025, 18:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/sigstore/timestamp-authorityGo<2.0.32.0.3
Identifiers
GHSA-4qg8-fj49-pxjh · CVE-2025-66564 · GO-2025-4192
Weakness (CWE)
CWE-405
Published
5 Dec 2025
Updated
10 Sept 2026

Machine-written summary

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

Sigstore Timestamp Authority versions before 2.0.3 allocate excessive memory when parsing requests. An attacker who can send a crafted request, either with an overly long OID containing many periods or a malformed Content-Type header, can cause memory allocation proportional to the input length. Upgrade to version 2.0.3. If the service runs behind a load balancer, configure it to reject excessively large requests.

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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0047, the 41st percentile, on 5 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.