Quick answers
- Is CVE-2026-81843 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81843 being exploited in the wild.
- How severe is CVE-2026-81843?
- Medium severity, with a CVSS score of 6.5, published 12 November 2026.
- Which products and versions are affected?
- Grafana <UNKNOWN>.
- Is there a fix for CVE-2026-81843?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81843 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81843?
- Check whether you run Grafana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
When an Elasticsearch data source uses a time-based index pattern, Grafana generates one index name per interval across the entire requested time range without enforcing limits, causing unbounded memory allocation. A user with Viewer role or higher can trigger this by submitting a query with an extreme time range; the memory exhaustion occurs before any request reaches Elasticsearch, making the attack effective regardless of cluster reachability. Static index-name configurations are not vulnerable.
Affected products
- Grafana Grafana <UNKNOWN>
Timeline
- 2026-11-12: disclosed