CVE-2026-21729: Unbounded Memory Allocation in Grafana Loki detected_fields Queries
Grafana Loki versions earlier than 3.7.0 contain an unbounded memory allocation vulnerability in detected_fields query processing. Queries specifying excessively large limits can trigger large memory allocations, potentially exhausting resources and disrupting service availability depending on the deployment strategy. The vulnerability is remotely exploitable with low attack complexity and requires neither authentication nor user interaction.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Excessive memory allocation can exhaust available resources, degrade performance, and cause denial of service. The extent of the availability impact depends on the Loki deployment strategy.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by enforcing strict query limits and resource controls around Loki query execution. Deployment-level safeguards such as memory limits, rate limiting, request validation, and isolation mechanisms may help reduce the likelihood or operational impact of large-limit queries causing service disruption. Specific vendor mitigation details are not currently available in the provided information.
Remediation
Patch, then assume compromise.
Upgrade Grafana Loki to version 3.7.0 or a later vendor-supported release containing the fix. Test and deploy the security update promptly.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-21729 exploited in the wild?
- As of Oct 19, 2026, Mallory has no reports of CVE-2026-21729 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-21729?
- As of Oct 19, 2026, Mallory has found no public exploit for CVE-2026-21729.
- Is there a patch for CVE-2026-21729?
- Upgrade Grafana Loki to version 3.7.0 or a later vendor-supported release containing the fix. Test and deploy the security update promptly.
- How severe is CVE-2026-21729?
- CVE-2026-21729 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.46% (40th percentile) as of Oct 19, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.