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).
Published: 2026-04-24
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Tempo allows users to query traces with an optional limit parameter. When a query specifies an excessively large limit, the service allocates a buffer proportional to that limit. This can exhaust available memory and cause the Tempo service to become unresponsive, leading to a denial‑of‑service attack.

Affected Systems

The affected product is Grafana:Tempo, a distributed tracing system. No specific version information is supplied, so all known publicly available releases are potentially vulnerable until a fix is released.

Risk and Exploitability

The CVSS score of 7.5 indicates a medium‑to‑high severity. The EPSS score is reported as < 1%, suggesting very low exploitation probability in the wild. Tempo is not listed in CISA’s KEV catalog. The vulnerability can be exploited by sending a crafted query with a very large limit from an external interface, assuming the attacker has query execution privileges. While the attack might require access to the Tempo query endpoint, the impact is significant because it can bring the service down.

Generated by OpenCVE AI on May 1, 2026 at 05:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Tempo to a version that includes the unbounded memory allocation fix
  • Set max_result_limit in the search configuration to 262,144 (or a lower safe value) to reserve a maximum buffer size for queries
  • Implement monitoring for memory usage spikes and enforce rate limiting on the query endpoint to mitigate potential abuse

Generated by OpenCVE AI on May 1, 2026 at 05:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-p4r4-xvrq-gvmc Grafana Tempo has an Uncontrolled Resource Consumption issue
History

Fri, 01 May 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

threat_severity

Important


Tue, 28 Apr 2026 01:45:00 +0000

Type Values Removed Values Added
First Time appeared Grafana
Grafana tempo
Vendors & Products Grafana
Grafana tempo

Fri, 24 Apr 2026 14:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-400
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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:

Updated: 2026-05-13T19:28:30.906Z

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

Link: CVE-2026-21728

cve-icon Vulnrichment

Updated: 2026-04-24T11:33:33.468Z

cve-icon NVD

Status : Awaiting Analysis

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

Modified: 2026-04-24T14:39:28.770

Link: CVE-2026-21728

cve-icon Redhat

Severity : Important

Publid Date: 2026-04-24T08:00:47Z

Links: CVE-2026-21728 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-05-01T05:45:10Z

Weaknesses