CVE-2026-21728GHSA-P4R4-XVRQ-GVMCGO-2026-5528
Tempo query limit results in unbounded memory allocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.8.4, 2.9.2, 2.10.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Grafana Tempo
From 1.3.0 · through 2.8.3; From 2.9.0 · through 2.9.1; From 2.10.0 · through 2.10.1
- Grafana Enterprise Traces (GET)
From 1.0.0 · through 2.8.7
- github.com/grafana/tempoGo
From 1.3.0 · fixed in 2.8.4
- github.com/grafana/tempoGo
From 2.9.0 · fixed in 2.9.2
- github.com/grafana/tempoGo
From 2.10.0 · fixed in 2.10.2
- github.com/grafana/tempoGo
From 1.3.0