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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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.
    (CVE-2026-21728)

ID	Name	Product	Family	Type	Severity
458633	Echo: github.com/grafana/tempo: security update to 2.8.4	Tenable Cloud Security	Echo Local Security Checks	Local	high
458633	Echo: github.com/grafana/tempo: security update to 2.8.4	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
441139	SCA: security update for github.com/grafana/tempo (GHSA-p4r4-xvrq-gvmc)	Tenable Cloud Security	SCA Checks	Local	high
441139	SCA: security update for github.com/grafana/tempo (GHSA-p4r4-xvrq-gvmc)	Tenable Self-Hosted Container Security	SCA Checks	Local	high

Detections

Analytics

CVE-2026-21728

high

Tenable Plugins

high

high

high

high