The full story
Tempo queries Vulnerability Tracked as CVE-2026-21728. No exploitation flag is present in the retained CyberDeltaForce data at this time; that status can change as vendor and threat-intelligence reporting develops. CVE-2026-21728 is a newly disclosed security weakness in the affected technology.
A security weakness in the affected technology is being tracked as CVE-2026-21728. Alternatively, automatically restart the service. The issue currently carries a HIGH 7 5 severity signal in the available reporting.
the development is primarily about a software weakness. Risk depends on whether the affected product and versions are present, whether the vulnerable function is reachable, whether exploitation is public or active, and what privileges the affected process carries. The issue currently carries a HIGH 7 5 severity signal in the CyberDeltaForce record.
The operational question is not simply the severity score, but whether the affected component is deployed, reachable, business-critical and protected by compensating controls. If you use the affected technology, first check whether the vulnerable component is actually present and reachable. The current severity assessment is HIGH 7 5.
Real risk depends on exposure, exploitability, compensating controls and the importance of the affected asset—not the CVSS number alone. The story is primarily about a software weakness. The issue is tracked as CVE-2026-21728.
The current record lists the severity as HIGH 7.5. The current record does not mark the vulnerability as actively exploited. Inventory affected products and versions.
Validate external and internal reachability of the vulnerable function. Apply the vendor fix or mitigation and review telemetry for exploitation indicators when available. NIST NVD published the primary report used for this article on Sep 7, 2026.
What the reporting is based on
CVE-2026-21728: Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strat
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.
Open sourceReporting ends here. The sections below are CyberDeltaForce analysis and defender-focused interpretation.
What this means
The story is primarily about a software weakness. Risk depends on whether the affected product and versions are present, whether the vulnerable function is reachable, whether exploitation is public or active, and what privileges the affected process carries.
What security teams should check now
- Inventory affected products and versions.
- Validate external and internal reachability of the vulnerable function.
- Apply the vendor fix or mitigation and review telemetry for exploitation indicators when available.
What is not yet confirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
