CVE-2026-21728
Tempo queries with large limits can cause large memory allocations …
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).
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- grafana.com/security/security-advisories/cve-2026-21728
- nvd.nist.gov/vuln/detail/CVE-2026-21728
- github.com/grafana/tempo/pull/6525
- github.com/grafana/tempo/commit/650eb1985a0776789c8564122990f588a742356f
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/
- github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/
- github.com/advisories/GHSA-p4r4-xvrq-gvmc
- nvd.nist.gov/vuln/detail/CVE-2026-21728
- cve.org/CVERecord?id=CVE-2026-21728
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.