GitHub Advisoryadvisory · Go
GHSA-p4r4-xvrq-gvmc Grafana Tempo has an Uncontrolled Resource Consumption issue
HIGH
Official page ↗
- Aliases
- CVE-2026-21728
- Ecosystem
- Go
- Packages
- github.com/grafana/tempo
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-400
- Reviewed
- 2026-05-05
Affected packages
• Go github.com/grafana/tempo: >= 1.3.0, < 2.8.4 → fixed in 2.8.4
• Go github.com/grafana/tempo: >= 2.9.0, < 2.9.2 → fixed in 2.9.2
• Go github.com/grafana/tempo: >= 2.10.0, < 2.10.2 → fixed in 2.10.2
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).
Related
Alias · CVE (1)
- CVE-2026-21728 Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its… vulnerability
Weakness · CWE (1)
- CWE-400 Uncontrolled Resource Consumption weakness
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-21728 advisory
- https://github.com/grafana/tempo/pull/6525 web
- https://github.com/grafana/tempo/commit/650eb1985a0776789c8564122990f588a742356f web
- https://github.com/grafana/tempo package
- https://github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-10.md?plain=1#L328 web
- https://github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-8.md?plain=1#L251 web
- https://github.com/grafana/tempo/blob/4dc3e5b0d3463a0b67498b662b85a148698b4afd/docs/sources/tempo/release-notes/version-2/v2-9.md?plain=1#L224 web
- https://grafana.com/security/security-advisories/cve-2026-21728 web