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).
Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18).
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GRAFANA
Published:
Updated: 2026-04-24T13:06:58.775Z
Reserved: 2026-01-05T09:26:06.215Z
Link: CVE-2026-21728
No data.
Status : Received
Published: 2026-04-24T09:16:03.710
Modified: 2026-04-24T09:16:03.710
Link: CVE-2026-21728
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.