Grafana Tempo vulnerabilities

3 vulnerabilities

Known vulnerabilities in Grafana Tempo, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

7.5CVE-2026-21728chainguardcommercial-grafana-11.6+33
EPSS score
0.64%
Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.6.5CVE-2026-27878chainguardcommercial-grafana-11.6+23
EPSS score
0.41%
A TraceQL query in Grafana Tempo with a large exemplars hint value can cause the Tempo instance to allocate an excessive amount of memory, resulting in an out-of-memory crash. This could allow an authenticated user to trigger a denial of service against the Tempo service.7.5CVE-2026-28377chainguardcommercial-grafana-11.6+33
EPSS score
0.16%
A vulnerability in Grafana Tempo exposes the S3 SSE-C encryption key in plaintext through the /status/config endpoint, potentially allowing unauthorized users to obtain the key used to encrypt trace data stored in S3. Thanks to william_goodfellow for reporting this vulnerability.