CVE-2026-21728: Vulnerability in Grafana Tempo
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.
AI Analysis
Technical Summary
This vulnerability in Grafana Tempo allows queries with large limits to trigger large memory allocations, which can degrade or disrupt service availability. The problem is related to resource exhaustion (CWE-400) and improper resource management (CWE-770). The CVSS 3.1 score is 7.5 (high), reflecting network attack vector, low complexity, no privileges or user interaction required, and impact on availability only. Mitigation can be achieved by setting a maximum result limit (e.g., max_result_limit=262144) in the search configuration or by automatically restarting the service to recover from memory exhaustion. Red Hat advisories mention security updates addressing this issue, but no direct patch version for Tempo is specified in the input data.
Potential Impact
The vulnerability can cause large memory allocations during Tempo queries with large limits, potentially leading to service unavailability or denial of service conditions. There is no reported impact on confidentiality or integrity. The impact is limited to availability degradation depending on deployment strategy.
Mitigation Recommendations
Mitigation is possible by configuring the max_result_limit parameter in the Tempo search configuration to limit the size of query results, for example setting it to 262144. Alternatively, implementing automatic service restarts can help recover from memory exhaustion. Red Hat advisories indicate security updates addressing this vulnerability; users should consult the referenced Red Hat errata for applicable patches or updates. Patch status is not explicitly confirmed in the input data; check vendor advisories for current remediation guidance.
CVE-2026-21728: Vulnerability in Grafana Tempo
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.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Grafana Tempo allows queries with large limits to trigger large memory allocations, which can degrade or disrupt service availability. The problem is related to resource exhaustion (CWE-400) and improper resource management (CWE-770). The CVSS 3.1 score is 7.5 (high), reflecting network attack vector, low complexity, no privileges or user interaction required, and impact on availability only. Mitigation can be achieved by setting a maximum result limit (e.g., max_result_limit=262144) in the search configuration or by automatically restarting the service to recover from memory exhaustion. Red Hat advisories mention security updates addressing this issue, but no direct patch version for Tempo is specified in the input data.
Potential Impact
The vulnerability can cause large memory allocations during Tempo queries with large limits, potentially leading to service unavailability or denial of service conditions. There is no reported impact on confidentiality or integrity. The impact is limited to availability degradation depending on deployment strategy.
Mitigation Recommendations
Mitigation is possible by configuring the max_result_limit parameter in the Tempo search configuration to limit the size of query results, for example setting it to 262144. Alternatively, implementing automatic service restarts can help recover from memory exhaustion. Red Hat advisories indicate security updates addressing this vulnerability; users should consult the referenced Red Hat errata for applicable patches or updates. Patch status is not explicitly confirmed in the input data; check vendor advisories for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GRAFANA
- Date Reserved
- 2026-01-05T09:26:06.215Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-21728","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22423","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22347","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:21769","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:23345","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:24503","vendor":"Red Hat"}]
Threat ID: 69eb2efb87115cfb68096492
Added to database: 04/24/2026, 08:51:07 UTC
Last enriched: 07/29/2026, 21:27:00 UTC
Last updated: 07/31/2026, 21:26:43 UTC
Views: 182
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.