CVE-2026-21728
Tempo query limit results in unbounded memory allocation
CVSS Score
7.5
EPSS Score
0.0%
EPSS Percentile
0th
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.
| Vendor | grafana |
| Product | tempo |
| Ecosystems | |
| Industries | Technology |
| Published | Apr 24, 2026 |
| Last Updated | Jul 24, 2026 |
Stay Ahead of the Next One
Get instant alerts for grafana tempo
Be the first to know when new high vulnerabilities affecting grafana tempo are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
CVSS v3 Breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability
Affected Versions
Grafana / Tempo
1.3.0 ≤ 2.8.3 2.9.0 ≤ 2.9.1 2.10.0 ≤ 2.10.1
Grafana / Enterprise Traces (GET)
1.0.0 ≤ 2.8.7
References
grafana.com: https://grafana.com/security/security-advisories/cve-2026-21728 access.redhat.com: https://access.redhat.com/security/cve/CVE-2026-21728 bugzilla.redhat.com: https://bugzilla.redhat.com/show_bug.cgi?id=2461395 security.access.redhat.com: https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21728.json access.redhat.com: https://access.redhat.com/errata/RHSA-2026:22423 access.redhat.com: https://access.redhat.com/errata/RHSA-2026:22347 access.redhat.com: https://access.redhat.com/errata/RHSA-2026:21769 access.redhat.com: https://access.redhat.com/errata/RHSA-2026:23345 access.redhat.com: https://access.redhat.com/errata/RHSA-2026:24503