Java4Shell (CVE-2026-114938) affects a specific accelerated Base64-decoding path, not every Java installation. Administrators should inventory the Java runtime each application actually uses, then check the CPU, JVM settings and input path against Red Hat’s four conditions before choosing a vendor fix or interim mitigation. Red Hat’s advisory details those conditions and response options.
Start with the runtime inside each application or container. A system-wide Java check can miss the copy that matters.
What has to align for Java4Shell exposure?
Red Hat describes Java4Shell as memory corruption in the accelerated OpenJDK Base64 decoder, with potential for a crash or remote code execution when the relevant conditions coincide. Its advisory identifies four prerequisites:
- The application runs OpenJDK 17.0.6 or later.
- The host is x86-64 and its CPU supports AVX-512 VBMI.
- The JVM is not configured to limit AVX to level 2 or lower.
- Attacker-controlled Base64 data reaches
java.util.Base64.Decoder.
Red Hat says ARM64 systems and x86-64 processors without AVX-512 VBMI are not known to be affected. It names Intel Ice Lake and later, and AMD Zen 4 and later, as examples of compatible processor generations.
The data can arrive through an application’s network-facing features. Red Hat names HTTP Basic credentials, SAML artifacts, CSRF tokens and MIME encoded words as possible paths; some may be decoded before a user authenticates. A login screen alone therefore does not rule out a reachable decoder.
Sergey Tech’s November 18 description said attack attempts had been reported, but no successful attack had been confirmed by that date.
How to check the Java runtimes your services use
Work through each application, container and appliance—not just the Java installations listed by the operating system. Red Hat recommends prioritizing internet-facing applications and authentication services.
- List the applications and services in scope. Include containers, vendor appliances and products that bundle Java. A launcher or server product may run its own runtime without a separate system-wide Java installation.
- Identify each runtime’s vendor and full build. Record the version used by that application, rather than assuming every service uses the host’s default Java.
- Check the host architecture and CPU features. The conditions in Red Hat’s advisory require x86-64 hardware with AVX-512 VBMI.
- Review the JVM’s AVX setting. Check whether the runtime is limited to AVX level 2 or lower; that setting changes whether the accelerated path can be used.
- Trace input to the decoder. Determine whether attacker-controlled Base64 can reach
java.util.Base64.Decoder, including through authentication or token handling. - Prioritize services that meet the conditions. Start with public-facing and authentication services, then follow each product vendor’s supported update or mitigation route.
A bundled runtime should be handled through the product vendor’s supported process. Updating a base Java image does not itself update every application image built from it: an Airbyte issue described older Corretto 21 runtimes persisting in platform images after a patched base image was available. The application image and its deployment may also need attention.
Which Oracle Java SE builds are listed for Java4Shell?
Oracle’s November 17, 2026 Critical Security Patch Update release notes list these Java SE builds for the four lines associated with Java4Shell fixes:
| Java SE line | Oracle build |
| 17 | 17.0.21.1 |
| 21 | 21.0.13.1 |
| 25 | 25.0.5.1 |
| 27 | 27.0.1.1 |
Oracle’s release notes date the CSPU to November 17 and list the Java SE builds. These version strings apply to Oracle Java SE; use the relevant vendor’s own update path for other Java distributions.
Red Hat’s advisory, updated November 19, identified RHEL 8, 9 and 10, and Red Hat builds of OpenJDK 17, 21 and 25, as affected products. On that date, Red Hat said it was expediting fixes and advised users to apply product updates when errata became available.
What interim JVM option does Red Hat recommend?
Red Hat’s preferred interim mitigation is -XX:-UseBASE64Intrinsics, which disables the accelerated Base64 implementation. Apply it to the affected JVM and restart that JVM for the option to take effect.
Red Hat also describes -XX:UseAVX=2 as an alternative that prevents AVX-512 use. Apply that option only on x86-64: Red Hat warns that an ARM64 JVM may not recognize it and may fail to start. The workaround is temporary; use the vendor’s permanent update when it is available for the product.
A runtime fix and a deployed-product fix are separate steps. After the vendor update, make sure the application or container using that runtime is rebuilt or updated and deployed; an individual Keycloak-related pull request documents an interim JVM flag and redeployment of pods.