Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18).
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Grafana | Tempo | unaffected |
|
No data.
No data.
No data.
Project Subscriptions
No data.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 24 Apr 2026 08:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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). | |
| Title | Tempo query limit results in unbounded memory allocation | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
MITRE
Status: PUBLISHED
Assigner: GRAFANA
Published:
Updated: 2026-04-24T08:00:47.074Z
Reserved: 2026-01-05T09:26:06.215Z
Link: CVE-2026-21728
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-04-24T09:16:03.710
Modified: 2026-04-24T09:16:03.710
Link: CVE-2026-21728
Redhat
No data.
OpenCVE Enrichment
No data.
No weakness.