
Tracked as CVE-2026-114938, and commonly known as Java4Shell or Java2Shell, the vulnerability carries a CVSS v4.0 score of 9.2 (Critical).
With Java powering enterprise applications, authentication services and critical infrastructure, organisations should immediately assess their exposure.
Java2Shell is a memory-corruption vulnerability affecting OpenJDK's hardware-accelerated Base64 decoder within the Java Virtual Machine (JVM).
The vulnerability occurs when specially crafted Base64 input triggers incorrect memory handling in the AVX-512 optimised decoding routine.
On affected systems, malformed input can overwrite adjacent heap memory, potentially allowing attackers to execute arbitrary code.
Successful exploitation may result in:
Researchers have demonstrated exploitation against Java-based products including Jenkins, Jira, Confluence, Keycloak and JFrog Artifactory.
Importantly, exploitation depends on the Java runtime, processor architecture and application exposure to untrusted Base64 input.
The vulnerability affects certain OpenJDK and Oracle Java distributions running on x86-64 processors supporting AVX-512 VBMI instructions.
Standard Java 8 and 11 builds and ARM64 environments are not affected by this specific flaw. Oracle's Java 8 Enterprise Performance Pack is an exception.
Other Java distributions require vendor-specific security updates.
For IT and Security Teams
For Business Leaders
Organisations should immediately upgrade affected Java runtimes to prevent potential remote code execution (RCE) through the vulnerable OpenJDK Base64 decoder.
Check the installed Java runtime:
java -version
Identify active Java processes:
ps aux | grep '[j]ava'
Review Java installations across application servers, containers, CI/CD pipelines and third-party products such as Jenkins, Jira and Keycloak.
Oracle released the following security updates on 17 November 2026:
Download the latest patched runtime from Oracle Java Downloads or your OpenJDK distribution vendor.
If an immediate upgrade is not possible, disable the vulnerable hardware-accelerated Base64 decoding routine by adding the following JVM startup parameter:
-XX:-UseBASE64Intrinsics
Example:
java -XX:-UseBASE64Intrinsics -jar application.jar
Alternatively, restrict JVM acceleration to AVX2:
java -XX:UseAVX=2 -jar application.jar
These workarounds prevent execution of the vulnerable AVX-512 code path on affected JVMs. They may affect performance and should not replace security patches.
Restart all affected Java applications after applying the mitigation.
Confirm the updated Java runtime using java -version and verify that all running JVM processes use the patched installation.
Rebuild affected container images, restart services and conduct vulnerability assessments to confirm remediation.
Emerging vulnerabilities such as Java2Shell demonstrate why continuous security testing is essential.
Blacklock combines automated vulnerability scanning, expert-led penetration testing and AI-assisted validation to help organisations identify security risks and verify remediation.
Our recent research covered HTTP2Shell: Brotli Remote Code Execution and PHP2Shell: Critical PHP Vulnerabilities.
Blacklock also provides free vulnerability detection tools:
Don't wait for your next penetration test to assess critical exposure.
Sign up now and explore Blacklock to strengthen your organisation's continuous security assurance.
Join our newsletter today and enhance your knowledge with valuable insights. It's quick, easy, and free!
