CVE-2026-21728 — Tempo query limit results in unbounded memory allocation

Affected: Grafana Tempo, Grafana Enterprise Traces (GET), Red Hat Multicluster Global Hub 1.3.4, Red Hat Multicluster Global Hub 1.4.5, Red Hat Multicluster Global Hub 1.6.5, Red Hat Multicluster Global Hub 1.7.0, Red Hat multicluster global hub 1.5.3, Red Hat Logging Subsystem for Red Hat OpenShift, Red Hat Multicluster Global Hub, Red Hat Advanced Cluster Management for Kubernetes 2 and 6 more

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.

GHSA-8396-jffm-qx4w — OpenFGA has cache-key delimiter injection in shared-iterator and v2 iterator that caches enables intra-store authorizat…

Affected: Go: github.com/openfga/openfga

### Description In OpenFGA, when iterator caching is enabled, two distinct check requests can produce the same cache key, leading to OpenFGA reusing an earlier cached result for a subsequent request.

### Preconditions This applies if the following preconditions are present:

- FGA runs with SharedIteratorCache enabled, - FGA runs with ListObjectsIteratorCache enabled.

### Fix Upgrade to version 1.16.0 or greater.

### Acknowledgements OpenFGA would like to thank @j4xT for the discovery and the detailed report.

Most recent entries from all

CVE-2026-21728 — Tempo query limit results in unbounded memory allocation

GHSA-8396-jffm-qx4w — OpenFGA has cache-key delimiter injection in shared-iterator and v2 iterator that caches enables intra-store authorizat…