High 8.1
Oracle / OpenJDK · Java (OpenJDK-based runtimes, Oracle Java SE, GraalVM) · CVE-2026-114938
Java4Shell flaw in Java 17 and later could let attackers run code on servers without a login
A memory flaw in the fast Base64 decoder built into Java, named Java4Shell by the researchers at Calif who reported it, can crash a Java application or let someone on the internet run code on it by sending crafted text, in some cases before any login. Java sits underneath a great deal of business software, and the researchers name Jira, Confluence, Jenkins and Keycloak among the applications reachable without a login. Oracle scores it 8.1 and calls it difficult to exploit; Red Hat's preliminary score is 9.8. No attacks were confirmed when The Hacker News reported on 18 November, and CISA has issued an alert urging prompt patching.
- Affected
- Java 17.0.6 and later, including Java 21, 25 and 27, from Oracle and other OpenJDK-based suppliers, plus Oracle GraalVM and Oracle's Java SE 8 Enterprise Performance Pack (8u511b33-perf). Only servers with Intel or AMD processors that support AVX-512 VBMI are exposed (Intel Xeon Ice Lake and newer, AMD Zen 4 and newer). Standard Java 8 and 11, ARM64 machines and older x86-64 processors are not known to be affected. Many products ship their own copy of Java, so the software you run may be affected even if you never installed Java yourself.
- What to do
- Update Java and restart every Java service. The Hacker News lists the fixed Oracle Java SE builds as 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 (8u513 for the Java 8 Performance Pack), Amazon Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4, and Azul Zulu 17.70.201, 21.54.201, 25.38.201 and 27.30.201. Red Hat said on 17 November that its fixes were being expedited and were not yet out. For products that bundle Java, install the supplier's update and rebuild container images. Until you can patch, Red Hat's interim mitigation is to start Java with -XX:-UseBASE64Intrinsics (preferred) or, on x86-64 only, -XX:UseAVX=2, and to remove the flag once the fixed build is in. On Linux, grep -o avx512vbmi /proc/cpuinfo shows whether the processor is the affected kind. If a supplier or host runs Java software for you, ask them to confirm it has been patched.General information summarised from the vendor's advisory at the time of writing, not professional advice. Check the vendor's current advisory before acting.
- Why it’s here
- A possible no-login takeover in the Java runtime behind a lot of business software, with a CISA alert and wide press coverage; fixes are out and no attacks are confirmed.
