Quick answers
- Is CVE-2026-102407 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102407 being exploited in the wild.
- How severe is CVE-2026-102407?
- Medium severity, with a CVSS score of 5.4, published 6 October 2026.
- Which products and versions are affected?
- Elasticsearch 7.17.5–7.17.29, 8.2.2–8.19.18, 9.0.0–9.3.7, 9.4.0–9.4.3.
- Is there a fix for CVE-2026-102407?
- Yes: fixed in Elasticsearch 8.19.19, 9.3.8, 9.4.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102407 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102407?
- 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.19, 9.3.8, 9.4.4
Technical details
The Modify Data Streams API in Elasticsearch fails to properly enforce role-based access control (ACLs), allowing authenticated users to modify data streams beyond their assigned privileges. An authenticated attacker with privileges over one resource can exploit this to modify a data stream they lack authorization for, either injecting malicious data or degrading search functionality. A fix is available in patched versions.
Affected products
- Elastic Elasticsearch 7.17.5–7.17.29, 8.2.2–8.19.18, 9.0.0–9.3.7, 9.4.0–9.4.3
Timeline
- 2026-10-06: disclosed