Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.
Exact source revision recorded 25 Oct 2026 05:17:32 UTC. It does not establish the source's current position. Latest evidence.
nvd · CVE-2026-21728
PublishedTempo 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.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-400 · CWE-770
Original publisher date fields
published: 2026-04-24T09:16:03.710
lastModified: 2026-09-09T13:18:44.397
1 source CPE criteria · context only
- cpe:2.3:a:grafana:tempo:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 24 Apr 2026 09:16:03 UTC
- Source modified
- 9 Sep 2026 13:18:44 UTC
- Observed here
- 25 Oct 2026 05:17:32 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H