CyberSecBulletin
CVE-2026-21728NVD status: Modified

Tempo: Uncontrolled Resource Consumption

Published Updated By the CyberSecBulletin desk

CVE-2026-21728 is a high-severity uncontrolled resource consumption vulnerability in Tempo from Grafana, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Tempo versions: 1.3.0 through 2.8.3; 2.9.0 through 2.9.1; 2.10.0 through 2.10.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.64% chance of exploitation within 30 days, higher than 51% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Tempo you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
GrafanaTempo1.3.0 through 2.8.3; 2.9.0 through 2.9.1; 2.10.0 through 2.10.1Not stated
GrafanaEnterprise Traces (GET)1.0.0 through 2.8.7Not stated
Red HatMulticluster Global Hub 1.3.4Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.4.5Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.6.5Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.7.0Not specified in the recordNot stated
Red HatRed Hat multicluster global hub 1.5.3Not specified in the recordNot stated
Red HatLogging Subsystem for Red Hat OpenShiftNot specified in the recordNot stated
Red HatMulticluster Global HubNot specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2Not specified in the recordNot stated
Red HatRed Hat Ceph Storage 5Not specified in the recordNot stated
Red HatRed Hat Ceph Storage 6Not specified in the recordNot stated
Red HatRed Hat Ceph Storage 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat OpenShift distributed tracing 3Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (grafana.com).

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA (grafana.com)
CVSS 3.17.5HighCNA

Official 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). Alternatively, automatically restart the service.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Tempo

All Tempo vulnerabilities

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.