Java4Shell (CVE-2026-114938): Our Exposure and Response

java4shell-cve-2026-114938

https://thehackernews.com
/2026/11/java4shell-cve-2026-114938-enables-pre.html

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'


>
AI NOTES from review :
 
The vulnerable code path in Java2Shell is specifically the AVX-512 Base64 intrinsic. Without avx512f, HotSpot wouldn't have activated that path in the first place. The   
 -XX:-UseBASE64Intrinsics flag we applied is still the right call (it's belt-and-suspenders, and the patch advisory covers all intrinsic paths), but your real-world     
 exposure was lower than a typical cloud VM with AVX-512 support.                                                                                                          
                                                                                                                                                                           
The OX Security analysis linked earlier noted "less than 0.12% of JVMs estimated at risk of RCE" — CPU capability is a big part of why that number is so low.
--

A critical Java vulnerability dubbed Java2Shell (CVE-2026-114938, CVSS 9.2) was disclosed on November 17, 2026. Here is a brief on what it is, whether the Gluebox infrastructure is affected, and what we are doing about it.

What is Java2Shell?

Java2Shell is a heap-based buffer overflow in the hardware-accelerated Base64 decoder built into OpenJDK's HotSpot JIT compiler. It affects OpenJDK versions 17, 21, 25, and 27. In the worst case, an attacker who can send crafted Base64-encoded input to a vulnerable Java process can achieve pre-authenticated remote code execution. CVSS score is 9.2 (Critical). No confirmed exploitation in the wild has been reported as of this writing.

Are we exposed?

This server runs two Java-based services: Apache Solr 8.11.2 (search indexing) and Apache Tika 2.9.4 (document parsing). Both run on a vulnerable JVM (OpenJDK 21.0.13.0.3).

The good news: both services are bound to 127.0.0.1 — they are not directly reachable from the internet. An attacker would need to already have local access or find an indirect path through the web application to reach them. That meaningfully reduces the risk compared to internet-exposed Java services.

Our remediation plan

  1. Immediate mitigation (today): Restart both Solr and Tika with the JVM flag -XX:-UseBASE64Intrinsics, which disables the vulnerable hardware-accelerated decoder. This is Oracle's recommended workaround and has no functional impact — only a minor performance trade-off on Base64 operations.
  2. Full patch: Ubuntu has not yet published OpenJDK 21.0.13.1 (the patched release) to its apt repositories. We will apply it as soon as it is available.

We will update this post when the patch is applied.