Skip to content
OpenAdvisories

Package · Go

github.com/grafana/tempo

3 known vulnerabilities.

3 results · Feed

  • Medium 6.5

    Tempo TraceQL query with exemplar hint could result in unbounded memory usage

    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 T…

  • High 7.5

    Tempo query limit results in unbounded memory allocation

    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). Alternat…

  • High 7.5

    S3 SSE-C Encryption Key Exposed in Plaintext via Config Endpoint (CVE-2025-41118 Pattern)

    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 reportin…