Quick answers
- Is CVE-2026-115715 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115715 being exploited in the wild.
- How severe is CVE-2026-115715?
- Medium severity, with a CVSS score of 6.5, published 3 November 2026.
- Which products and versions are affected?
- Elasticsearch 8.0.0 to 8.19.23; 9.0.0 to 9.4.8; 9.5.0 to 9.5.5.
- Is there a fix for CVE-2026-115715?
- Yes: fixed in Elasticsearch 8.19.24, 9.4.9, 9.5.6. Until then: Stop using the koelnerphonetik and haasephonetik encoders in index analyzers. To change an analyzer for an existing field, create a new index with an updated mapping and reindex the data into it. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115715 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-115715?
- 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.24, 9.4.9, 9.5.6
Stop using the koelnerphonetik and haasephonetik encoders in index analyzers. To change an analyzer for an existing field, create a new index with an updated mapping and reindex the data into it.
Technical details
A resource allocation vulnerability (CWE-770) exists in the analysis-phonetic plugin's koelnerphonetik and haasephonetik encoders, which fail to throttle processing of specially crafted input values. An authenticated attacker with index write or search permissions can trigger heap memory exhaustion on an Elasticsearch node by submitting malicious phonetic input, causing denial of service; the issue is fixed in versions 8.19.24, 9.4.9, and 9.5.6.
Affected products
- Elastic Elasticsearch 8.0.0 to 8.19.23; 9.0.0 to 9.4.8; 9.5.0 to 9.5.5
Timeline
- 2026-11-03: disclosed