Elastic is aware of a remote code execution vulnerability (CVE-2026-114938, also known as Java4Shell) affecting OpenJDK and Oracle Java SE that was disclosed on November 17, 2026.
Elastic is evaluating impact across our full suite of products and infrastructure and will release further details as applicable and when available.
Elasticsearch
- Elastic has confirmed that Elasticsearch versions 7.17.3 and later are vulnerable to this CVE and that the vulnerability can be exploited by an authenticated user with at least “read” access to achieve Remote Code Execution (RCE) and by unauthenticated actors to achieve Denial of Service (DoS) against Elasticsearch nodes.
Elastic Cloud
-
Elastic Cloud Serverless is only vulnerable in extremely rare cases and we are deploying a hotfix to mitigate those rare cases during Wednesday 18th November. Elastic is evaluating potential configuration options to mitigate this vulnerability for Elastic Cloud Hosted and self-managed customers, with details for self-managed customers shared below. Elastic is also preparing an update to address this vulnerability by updating the bundled JDK to 27.0.1.1+4. This is expected to ship with the upcoming 8.19.26, 9.4.10, 9.5.7, and 9.6.0 Elastic releases.
-
In parallel, Elastic is evaluating impact across our full suite of products and infrastructure and will release further details when available.
Mitigation for Self-Managed Elasticsearch Customers
-
Self-managed customers can mitigate this vulnerability by disabling the affected JVM optimization. Only Elasticsearch nodes on
x86-64 CPUsthat support theAVX512_VBMIinstruction set are affected (for example Intel Xeon Ice Lake and later, and AMD Zen 4 and later). Nodes on ARM CPUs and on olderx86 CPUsare not affected. -
To check a host, run
grep -c avx512vbmi /proc/cpuinfo; a result greater than 0 means the host is affected. -
To apply the mitigation, create a file in the
config/jvm.options.d/directory of each affected node (for exampleconfig/jvm.options.d/cve-2026-114938.options) that contains the single line-XX:-UseBASE64Intrinsics, then restart the node. Docker users can mount this file into/usr/share/elasticsearch/config/jvm.options.d/, and ECK users can add the option to theES_JAVA_OPTSenvironment variable in the pod template. A rolling restart avoids cluster downtime. To confirm the mitigation is active, check that-XX:-UseBASE64Intrinsicsappears in thejvm.input_argumentsof each node in the output ofGET _nodes/jvm. -
Customers should still upgrade to a release that includes the updated bundled JDK as soon as it is available.