github.com/sigstore/timestamp-authority/v2
Affected
- introduced
0, fixed2.1.0(semver)
Fixed versions
2.1.0
Fix
- Fixed version
2.1.0go get github.com/sigstore/timestamp-authority/[email protected]
Advisory
Also known as: CVE-2026-49835, GO-2026-5851
Sigstore Timestamp Authority has OOM due to unbounded metric label cardinality
Impact
An unauthenticated remote attacker can trigger unbounded memory growth on the timestamp authority server.
This vulnerability exists because the global wrapMetrics middleware records the raw HTTP request path (r.URL.Path) and raw HTTP request method (r.Method) as Prometheus labels for latency and request count metric vectors. Since this middleware runs before standard routing occurs, it executes for all incoming requests, including those for unmatched paths (yielding 404 responses) or arbitrary request methods. The Prometheus library registers a new, permanent time-series entry for every distinct label combination. An attacker can continuously issue requests containing random paths (e.g., /api/v1/timestamp/<uuid>) or random HTTP methods to exhaust system memory.
Patches
This issue has been patched by limiting the metric label values to a strict allowlist of expected paths (/ping, /api/v1/timestamp, /api/v1/timestamp/certchain) and expected HTTP methods (GET, POST, HEAD, OPTIONS). Unrecognized paths or methods are normalized to a static string ("unrecognized").
Users should update to version v2.0.7 or later.
Workarounds
Medium Basis: The source's own band: MODERATE
0, fixed 2.1.0 (semver)2.1.0
2.1.0go get github.com/sigstore/timestamp-authority/[email protected]0, last affected 1.2.9 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0