GPU VulnDB

Database/Control plane, storage & DevOps

Sigstore Timestamp Authority: unauthenticated requests mint unbounded Prometheus series until memory is exhausted

CVSS 7.5CVE-2026-49835Control plane, storage & DevOpscurated

Impact

The global wrapMetrics middleware records the raw request path (r.URL.Path) and raw method (r.Method) as Prometheus labels on the latency and request-count vectors, and does so before routing - so values that match no route are still turned into labels. An unauthenticated client sending requests to /api/v1/timestamp/<random-uuid>, or with random HTTP methods, creates permanent time-series entries that are never reclaimed, until the TSA process exhausts memory and dies. Two things break for an operator: the timestamp authority itself, which stalls the signing and attestation steps of image and model-artifact pipelines that depend on RFC 3161 timestamps, and the Prometheus server scraping it, which ingests the cardinality bomb and can be pushed over its own memory limits - taking fleet monitoring down with the service that was attacked. Fixed in 2.1.0.

Who can reach it

Any unauthenticated client that can reach the TSA's HTTP listener. No credentials, no valid timestamp request, no specific path required - arbitrary paths are the attack. Exposure is whatever the listener is bound to; an internet-exposed or tenant-reachable TSA is directly at risk, one behind mTLS or an internal-only ingress much less so.

What to do

Upgrade to timestamp-authority 2.1.0 and restart the service - a daemon restart of a control-plane component, no node drain. Until you can, put the listener behind authentication or an ingress that rejects unrouted paths and non-standard methods, cap the TSA's memory so it restarts instead of taking the node, and apply a metric_relabel_config on the Prometheus side to drop the path/method labels so an attempt cannot also damage your monitoring.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.