Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Grafana Tempo
Default version status: unaffected
1.3.0 to ≤ 2.8.3affected2.9.0 to ≤ 2.9.1affected2.10.0 to ≤ 2.10.1affected
Grafana Enterprise Traces (GET)
Default version status: unaffected
1.0.0 to ≤ 2.8.7affected
References
- https://grafana.com/security/security-advisories/cve-2026-21728 ↗
- https://access.redhat.com/security/cve/CVE-2026-21728 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2461395 ↗
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21728.json ↗
- https://access.redhat.com/errata/RHSA-2026:22423 ↗
- https://access.redhat.com/errata/RHSA-2026:22347 ↗
- https://access.redhat.com/errata/RHSA-2026:23345 ↗
- https://access.redhat.com/errata/RHSA-2026:24503 ↗
- https://access.redhat.com/errata/RHSA-2026:21769 ↗