7.5highHigh
CVE-2026-21728
Grafana Tempo
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.
What the metrics mean
- It is reachable over a network, without needing local access.
- For an attacker who can reach it, no special conditions are needed to exploit it.
- To exploit it, no account is needed.
- Beyond that, no action by a user is required.
Scoring
- CVSS
- 7.5 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Weakness
- CWE-400
- Assigned by
- security@grafana.com
Dates
- Published
- 2026-04-24
- Last modified
- 2026-08-24
- Sources
- NVD
Affected products
- Grafana Tempo1.3.0 - 2.8.4, 2.9.0 - 2.9.2, 2.10.0 - 2.10.2
As listed in the NVD configuration data. Not a statement about your estate.
References
- https://grafana.com/security/security-advisories/cve-2026-21728
- https://access.redhat.com/errata/RHSA-2026:21769
- https://access.redhat.com/errata/RHSA-2026:22347
- https://access.redhat.com/errata/RHSA-2026:22423
- https://access.redhat.com/errata/RHSA-2026:23345
- https://access.redhat.com/errata/RHSA-2026:24503
- https://access.redhat.com/security/cve/CVE-2026-21728
- https://bugzilla.redhat.com/show_bug.cgi?id=2461395
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21728.json