Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.1.0, the global wrapMetrics middleware records raw HTTP request path r.URL.Path and raw HTTP request method r.Method as Prometheus labels for latency and request count metric vectors before routing, allowing an unauthenticated remote attacker to issue requests with random paths such as /api/v1/timestamp/<uuid> or random HTTP methods and create unbounded permanent time-series entries that exhaust memory. This issue is fixed in version 2.1.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/sigstore/timestamp-authority/commit/506ec57b6ac2ea1e4739322e47453469425b69b5 Patch
- https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-9c54-x2g4-v92j Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.5 · linuxfoundationNVD modified 2026-10-24 20:10
Affected (CPE criteria) 1
cpe:2.3:a:linuxfoundation:sigstore_timestamp_authority:*:*:*:*:*:*:*:*
References 3
- https://github.com/sigstore/timestamp-authority/commit/506ec57b6ac2ea1e4739322e47453469425b69b5 Patch
- https://github.com/sigstore/timestamp-authority/releases/tag/v2.1.0 Product, Release Notes
- https://github.com/sigstore/timestamp-authority/security/advisories/GHSA-9c54-x2g4-v92j Mitigation, Vendor Advisory