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
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Grafana | Tempo | 1.3.0 – ≤ 2.8.3, 2.9.0 – ≤ 2.9.1, 2.10.0 – ≤ 2.10.1 | — |
| Grafana | Enterprise Traces (GET) | 1.0.0 – ≤ 2.8.7 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | grafana-12.3 +2 | No fix yet | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | github.com/grafana/tempo | >= 1.3.0, < 2.8.4 | 2.8.4 | GHSA-p4r4-xvrq-gvmc |
| Go | github.com/grafana/tempo | >= 2.9.0, < 2.9.2 | 2.9.2 | GHSA-p4r4-xvrq-gvmc |
| Go | github.com/grafana/tempo | >= 2.10.0, < 2.10.2 | 2.10.2 | GHSA-p4r4-xvrq-gvmc |
| Go | github.com/grafana/tempo | >= 1.3.0 | — | GO-2026-5528 |
Advisories 2
- openSUSE-SU-2026:21483-1 Security update for govulncheck-vulndb SUSE / openSUSE Security Updates · Jul 31, 2026
- WID-SEC-2026-2342 Grafana Tempo: Mehrere Schwachstellen ermöglichen Denial of Service BSI CERT-Bund (WID) · Jul 14, 2026
References
- https://grafana.com/security/security-advisories/cve-2026-21728 vendor-advisory