Elastic flaw allows remote code execution in Elasticsearch and Logstash
CERT-FR has flagged CVE-2026-114938, a flaw in Elasticsearch, Logstash and Elastic Cloud Hosted that enables remote code execution and denial of service. Organisations running these products on versions earlier than 9.5.7, 9.4.10 or 8.19.26 are affected.
What to do now
- Product
- Elasticsearch, Logstash, Elastic Cloud Hosted
- Affected versions
- Elasticsearch, Logstash and Elastic Cloud Hosted: 9.5.x before 9.5.7, 9.x before 9.4.10, versions before 8.19.26
- Fixed in
- 9.5.7, 9.4.10 and 8.19.26
- CVE
- CVE-2026-114938
France's CERT-FR issued advisory CERTFR-2026-AVI-1578 on 19 November 2026. It covers a vulnerability in several Elastic products, tracked as CVE-2026-114938. The advisory is based on Elastic security bulletin 391703, released by the vendor a day earlier. The URL of that bulletin refers to the issue as "Java4Shell".
According to CERT-FR, a remote attacker can use the flaw to run arbitrary code on an affected system or to cause a denial of service. The advisory does not describe the conditions for exploitation. It does not say whether authentication is required, nor whether the flaw is being exploited in the wild.
Three products are listed: Elasticsearch, Logstash and the managed Elastic Cloud Hosted service. For each one, three ranges are vulnerable: 9.5.x before 9.5.7, other 9.x releases before 9.4.10, and any version earlier than 8.19.26.
CERT-FR points readers to Elastic's bulletin for the patches. The version thresholds in the advisory (9.5.7, 9.4.10 and 8.19.26) are the releases to target. The advisory does not explain how updates are rolled out to Elastic Cloud Hosted deployments.
Elasticsearch and Logstash often handle logs and sensitive business data. They are sometimes reachable from wide internal networks. Remote compromise of these components could therefore seriously affect both data confidentiality and service availability.
What to do now
- Inventory every Elasticsearch and Logstash instance and every Elastic Cloud Hosted deployment, recording the exact version of each.
- Upgrade to 9.5.7, 9.4.10 or 8.19.26 depending on your branch, following Elastic bulletin 391703.
- For Elastic Cloud Hosted, confirm in your console or with Elastic that your deployments run a fixed version.
- Until patched, restrict network access to these services to the systems that need it, as general good practice.
- Review logs and running processes on affected servers for unusual activity since the flaw was disclosed.