AI NewsInfrastructureAnnouncement
Elastic lists Elasticsearch and Logstash as vulnerable to Java4Shell
Elastic says that Elasticsearch 7.17.3 and later and Logstash 8.6.2 and later are vulnerable to Java4Shell, CVE-2026-114938. The fix is in planned releases 8.19.26, 9.4.10, 9.5.7 and 9.6.0.

Why it mattersA Java flaw is now an Elasticsearch problem on modern Intel and AMD servers. One JVM flag stops it. The real fix is a cluster upgrade.
Elastic has told its customers that Elasticsearch and Logstash are vulnerable to Java4Shell, CVE-2026-114938. The company posted the advisory on 18 November 2026. The flaw is in the Base64 decoder in OpenJDK on x86-64 chips with AVX-512 VBMI. OpenJDK and Oracle disclosed it on 17 November.
Elastic says Elasticsearch versions 7.17.3 and later are vulnerable. Logstash 8.6.2 and later are vulnerable. Logstash 7.17.x and any Logstash version before 8.6.2 is not affected. The post says Elastic Cloud Serverless, Elastic Cloud Hosted and other managed products are "being updated with the patched JDK".
Which machines matter
The flaw only hits x86-64 chips that support the AVX512_VBMI instruction set. Elastic names Intel Xeon Ice Lake and newer and AMD Zen 4 and newer. ARM clusters are not affected. Older Intel and AMD chips without AVX-512 VBMI are not affected. A team running Elasticsearch on a mix of chip generations has fewer nodes to patch than it first looks.
Elasticsearch runs code, Logstash crashes
Elastic describes the attack on each product. On Elasticsearch, the attacker must be signed in and hold at least read access. The result is remote code execution on the server. An unauthenticated user can still cause a denial of service. Logstash needs the Elastic Integration filter and Base64 fields from an untrusted source. On Logstash the result is a crash.
What to do tonight
Elastic gives two options. Add -XX:-UseBASE64Intrinsics to the JVM options to turn the broken optimisation off. Alternatively, download a JDK that does not include the flaw. The post names JDK 27.0.1.1+4 as the fixed build to bundle. Both options need a restart of the Java process.
The permanent fix is Elasticsearch 8.19.26, 9.4.10, 9.5.7 or 9.6.0. Elastic says those releases are expected. None had been released at the time of the post. A team running its own cluster should start with the JVM flag tonight. The version upgrade comes next.
Where the risk is highest
The two conditions that matter are the chip and the sign-in. The worst case is a public cluster on recent Intel or AMD hardware. Any read access given to a low-trust account is enough for the attacker to take over. That case covers most managed search installations and many logging pipelines. A Logstash that reads events from external systems through the Elastic Integration filter is in the same group.
A team running Elasticsearch on ARM, on Graviton or on older x86 hardware can wait. Every other cluster needs the flag in jvm.options this week.
Source
Elastic: Java4Shell Remote Code Execution (RCE) Vulnerability - CVE-2026-114938.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.

