Description (CNA)
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 (CNA)
| Vendor / product | Versions |
|---|---|
| Grafana / Tempo | affected 1.3.0 through 2.8.3; affected 2.9.0 through 2.9.1; affected 2.10.0 through 2.10.1 |
| Grafana / Enterprise Traces (GET) | affected 1.0.0 through 2.8.7 |
CWE
No CWE identifiers supplied.
References
ADP enrichment
No English description supplied.
No references supplied.
A flaw was found in Tempo. A remote attacker can exploit this vulnerability by sending large queries to the Tempo service. This can lead to excessive memory allocations, potentially causing a Denial of Service (DoS) by impacting the availability of the service.
- 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