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_resul…
High CVSS 7.5
Summary
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.
In-depth triage · Auto channel
No in-depth report has been generated yet (DR-003 v2 AI pipeline is under construction).
Affected products
- :
Lint boundary warnings (1)
The following non-blocking warnings were raised during the lint phase of this triage (e.g. reference URLs not yet on the allowlist). They do not affect entry usability and are disclosed for transparency (see DR-002).
-
REF_URL_NOT_ALLOWLISTEDurl not in allowlist: https://grafana.com/security/security-advisories/cve-2026-21728
Sources
- NVD DATABASE
Original Links
- https://grafana.com/security/security-advisories/cve-2026-21728 Broken Link
- https://access.redhat.com/errata/RHSA-2026:21769
- https://access.redhat.com/errata/RHSA-2026:22347
- https://access.redhat.com/errata/RHSA-2026:22423
- https://access.redhat.com/errata/RHSA-2026:23345
- https://access.redhat.com/errata/RHSA-2026:24503
- https://access.redhat.com/security/cve/CVE-2026-21728
- https://bugzilla.redhat.com/show_bug.cgi?id=2461395
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21728.json
Timeline
- nvd_ingest NVD