Advisoriesby IbisTempoGHSA-p4r4-xvrq-gvmc
Grafana Tempo has an Uncontrolled Resource Consumption issue
Fix: upgrade to 2.8.4 or later (3 fixed versions below)
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).
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| github.com/grafana/tempo Go | >= 1.3.0, < 2.8.4 | 2.8.4 |
| >= 2.9.0, < 2.9.2 | 2.9.2 | |
| >= 2.10.0, < 2.10.2 | 2.10.2 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-400
- Also known as
- CVE-2026-21728, GO-2026-5528
- nvd.nist.gov/vuln/detail/CVE-2026-21728
- github.com/grafana/tempo/pull/6525
- github.com/grafana/tempo/commit/650eb1985a0776789c8564122990f588a742356f
- github.com/grafana/tempo
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-10.md?plain=1#L328
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-8.md?plain=1#L251
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-9.md?plain=1#L224
- grafana.com/security/security-advisories/cve-2026-21728