Quick answers
- Is CVE-2026-103008 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103008 being exploited in the wild.
- How severe is CVE-2026-103008?
- Medium severity, with a CVSS score of 6.5, published 6 October 2026.
- Which products and versions are affected?
- Elasticsearch 8.12.0 to 8.19.22; 9.0.0 to 9.4.7; 9.5.0 to 9.5.4.
- Is there a fix for CVE-2026-103008?
- Yes: fixed in Elasticsearch 8.19.23, 9.4.8, 9.5.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103008 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-103008?
- 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: Elasticsearch 8.19.23, 9.4.8, 9.5.5
Technical details
The vulnerability is an uncontrolled recursion flaw (CWE-674) in the geometry serialization logic for scripted runtime fields. Unlike geometry supplied as text input, which enforces a nesting-depth limit, geometry constructed programmatically from script output has no recursion bound. An authenticated attacker with read access to an index can trigger stack exhaustion and denial of service by submitting a request with a script that produces arbitrarily nested geometry structures.
Affected products
- Elastic Elasticsearch 8.12.0 to 8.19.22; 9.0.0 to 9.4.7; 9.5.0 to 9.5.4
Timeline
- 2026-10-06: disclosed: CVE-2026-103008 published