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
grafana: tempo
References9
- grafana.com/security/security-advisories/cve-2026-21728 Broken Link
- access.redhat.com/errata/RHSA-2026:21769
- access.redhat.com/errata/RHSA-2026:22347
- access.redhat.com/errata/RHSA-2026:22423
- access.redhat.com/errata/RHSA-2026:23345
- access.redhat.com/errata/RHSA-2026:24503
- access.redhat.com/security/cve/CVE-2026-21728
- bugzilla.redhat.com/show_bug.cgi?id=2461395
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21728…
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 51 · as of 13 November 2026
- CWE
- CWE-400CWE-770
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.