Answer in brief
CVE-2026-21728 records a High severity (CVSS 7.5) vulnerability in Tempo query limit results in unbounded memory allocation. The current sources do not mark it as known exploited. The current feed maps Grafana/Enterprise Traces (GET) (generic), Grafana/Tempo (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-21728 records a High severity (CVSS 7.5) vulnerability in Tempo query limit results in unbounded memory allocation. The current sources do not mark it as known exploited. The current feed maps Grafana/Enterprise Traces (GET) (generic), Grafana/Tempo (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Grafana/Enterprise Traces (GET) (generic), Grafana/Tempo (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Grafana/Enterprise Traces (GET)generic | 1.0.0 | Not reported |
| Grafana/Tempogeneric | 1.3.0 || 2.9.0 || 2.10.0 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 29, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Grafana/Enterprise Traces (GET) (generic), Grafana/Tempo (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Grafana/Enterprise Traces (GET)generic | 1.0.0 | Not reported |
| Grafana/Tempogeneric | 1.3.0 || 2.9.0 || 2.10.0 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 29, 2026
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.
Quoted source text, attributed separately from HOL analysis.