CVE-2026-27878: Tempo TraceQL query with exemplar hint could result in unbounded memory usage
A TraceQL query in Grafana Tempo with a large exemplars hint value can cause the Tempo instance to allocate an excessive amount of memory, resulting in an out-of-memory crash. This could allow an authenticated user to trigger a denial of service against the Tempo service.
Security readout for executives and security teams
Plain-English summary
An authenticated user can submit a TraceQL query with an oversized exemplar hint that makes Grafana Tempo allocate excessive memory and crash. The business impact is service disruption to tracing/observability, not data theft or code execution based on the provided sources.
Executive priority
Treat this as a moderate operational resilience issue. Prioritize environments where tracing is business-critical or broadly accessible to internal users, because exploitation could interrupt observability during incidents.
Technical view
CVE-2026-27878 is a CWE-400 resource-consumption issue in Grafana Tempo and Grafana Enterprise Traces. The reported vector is network-accessible with low attack complexity and low privileges required. Impact is availability only, with CVSS 3.1 score 6.5.
Likely exposure
Exposure appears limited to Grafana Tempo 2.6.0 and Grafana Enterprise Traces 2.6.1 where authenticated users can run TraceQL queries against the service.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation evidence. It describes an authenticated denial-of-service condition through excessive memory allocation.
Researcher notes
The provided evidence supports authenticated availability impact only. Do not assume unauthenticated reachability, data exposure, code execution, or confirmed exploitation without additional vendor or threat-intelligence evidence.
Mitigation direction
Check Grafana’s advisory for fixed versions or vendor-recommended mitigation.
Upgrade affected Tempo or Enterprise Traces deployments when Grafana provides a corrected release.
Restrict TraceQL query access to trusted authenticated users.
Monitor Tempo memory limits, restarts, and out-of-memory events.
Review rate limits or query controls available in your deployment.
Validation and detection
Inventory Grafana Tempo and Enterprise Traces versions across environments.
Confirm whether Tempo 2.6.0 or GET 2.6.1 is deployed.
Review who can submit TraceQL queries.
Check logs and metrics for unusual memory spikes or OOM crashes.
Verify remediation against Grafana’s advisory after applying updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.