Quick answers
- Is CVE-2026-103006 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103006 being exploited in the wild.
- How severe is CVE-2026-103006?
- Medium severity, with a CVSS score of 6.5, published 6 October 2026.
- Which products and versions are affected?
- Elasticsearch 8.0.0 through 8.19.20, 9.0.0 through 9.4.5, 9.5.0 through 9.5.1.
- Is there a fix for CVE-2026-103006?
- Yes: fixed in 8.19.21, 9.4.6, 9.5.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103006 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-103006?
- Check whether you run Elasticsearch 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.
How to fix
- Fixed in: 8.19.21, 9.4.6, 9.5.2
Technical details
The vulnerability is an uncontrolled recursion flaw (CWE-674) in Elasticsearch's search aggregation processing. An authenticated attacker with read access to a single index can submit a request with deeply nested aggregation definitions, triggering unbounded recursive execution that exhausts server resources and terminates the node. The vulnerable code path is part of the search aggregation functionality enabled by default.
Affected products
- Elastic Elasticsearch 8.0.0 through 8.19.20, 9.0.0 through 9.4.5, 9.5.0 through 9.5.1
Timeline
- 2026-10-06: disclosed