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).
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

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GRAFANA

Published: 2026-04-24T08:00:47.074Z

Updated: 2026-04-24T08:00:47.074Z

Reserved: 2026-01-05T09:26:06.215Z

Link: CVE-2026-21728

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-04-24T09:16:03.710

Modified: 2026-04-24T09:16:03.710

Link: CVE-2026-21728

cve-icon Redhat

No data.