Security Advisory: CVE-2026-114938 – Java Base64 Decoder Heap Overflow ("Java4Shell")

Date Published: 2026-11-19

CVE Reference: CVE-2026-114938

Component: HotSpot JVM (OpenJDK and its builds), AVX-512 Base64 decode intrinsic used by java.util.Base64

Affected versions: JDK 17.0.6 and later, JDK 21, 25 and 27, on x86-64 CPUs with AVX-512 VBMI

Fixed versions: JDK 17.0.21.1, 21.0.13.1 and 25.0.5.1, from Oracle, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft and the Red Hat build of OpenJDK. Red Hat Enterprise Linux system packages: pending

Skyve status: Affected on vulnerable JDK and CPU combinations, including the default configuration. Apply the JVM mitigation below to all deployments

Summary

On 17 November 2026, Calif disclosed "Java4Shell" (CVE-2026-114938). It is a heap overflow in the Java virtual machine, not in a library. Modern JVMs replace java.util.Base64 decoding with a hand-tuned machine-code routine (an "intrinsic") on CPUs that support it. The AVX-512 version of that routine can write past the end of its output buffer when it is given crafted input.

Three conditions all have to be true for an application to be exposed:

  1. The JDK. JDK 17.0.6 or later, 21, 25 or 27. Red Hat lists Java 8 and 11 as not affected, though some reports disagree.
  2. The CPU. x86-64 with AVX-512 VBMI. That means Intel Ice Lake or Sapphire Rapids and later, or AMD Zen 4 and later, which includes many current cloud instance types. ARM servers (for example AWS Graviton and Apple silicon) are not affected.
  3. The API. Untrusted data has to reach the basic decoder (Base64.getDecoder()) or the URL decoder (Base64.getUrlDecoder()). The MIME decoder (Base64.getMimeDecoder()) does not use the vulnerable routine.

The impact is disputed. Calif reports remote code execution, but it depends on heap grooming specific to each application. Equixly argues that a crash, and so a denial of service, is the realistic outcome. As of today we are not aware of any exploitation in the wild, and the CVE is not in CISA's Known Exploited Vulnerabilities catalogue. A JVM crash takes down every application on that server, so we are treating it seriously regardless.

Skyve Impact

Current Skyve versions require Java 17 or later, so most Skyve applications run on an affected JDK. Whether a particular application is exposed depends on its CPU and on whether untrusted input reaches one of the affected decoders. We reviewed every place the Skyve platform, and the Spring Security framework it uses, decodes Base64, and how a request reaches each one.

A default Skyve application has an unauthenticated path to the affected decoder: the remember-me cookie.

Skyve enables Spring Security's "remember me" login by default, in both SpringSecurityConfig and older security.xml files. When a request arrives without a session and carries a remember-me cookie, Spring Security decodes the cookie with Base64.getDecoder() before it checks whether the token is valid. Anyone who can send a request to the application can supply that cookie, on any page, without logging in. So if the JVM and CPU are in the affected range, a default Skyve application should be considered exposed.

Optional configurations add further unauthenticated paths:

  • Single customer Basic authentication. Skyve includes an optional SingleCustomerBasicAuthenticationFilter, offered as a commented-out example in SpringSecurityConfig and older security.xml files. It decodes the Authorization header with Base64.getDecoder() before the user is authenticated. If your project has enabled it, the vulnerable decoder is reachable by anyone who can reach your server.
  • Spring Security Basic authentication. If your project has re-enabled httpBasic() in SpringSecurityConfig, or uses <http-basic/> in a Spring security.xml, Spring Security decodes the header with java.util.Base64 before login, with the same exposure.
  • Your own code and libraries. Any custom code or third-party library that decodes request data (headers, query parameters, tokens, uploads) with Base64.getDecoder() or Base64.getUrlDecoder() is a potential path, whether or not it requires a login first.

The rest of Skyve's Base64 handling is not affected:

  1. Skyve's REST Basic authentication filter uses the MIME decoder. The BasicAuthFilter used to protect REST endpoints decodes the Authorization header with Base64.getMimeDecoder(), which is not affected.
  2. OAuth and JWT tokens are decoded by the Nimbus library, which uses its own Base64 code rather than java.util.Base64.
  3. Other Base64 handling in Skyve. Report directives only encode Base64, which is a different routine. Session state and legacy password handling use Apache Commons Codec, and SVG sanitising uses the MIME decoder.

We have not demonstrated an exploit against Skyve. Given the disputed impact, the most likely realistic outcome is that a crafted request crashes the JVM.

Recommended Actions

The JVM flag below removes the vulnerable code path completely, whatever your configuration. Because the default configuration is exposed, we recommend it for every Skyve deployment on x86-64 until a fixed JDK is installed.

  • Turn off the Base64 intrinsics now. Add -XX:-UseBASE64Intrinsics to your JVM options. On a standard WildFly install, add it to JAVA_OPTS (for example in bin/standalone.conf). On a container or runtime without a shell, add it to the java command line or the JAVA_TOOL_OPTIONS environment variable. java.util.Base64 then uses its plain Java code. The performance cost is small for typical Skyve workloads. Restart the server for the flag to take effect.
  • If you can't change JVM options straight away, turn off remember-me as a stopgap. Remove the .rememberMe(...) block from your project's SpringSecurityConfig (or <remember-me> from an older security.xml) and redeploy. Alternatively, have your reverse proxy or firewall strip the remember cookie from incoming requests. Users will have to log in again after each session ends. This closes the default path only, not the optional paths above or any in your own code, so apply the JVM flag as soon as you can.
  • Don't use -XX:UseAVX=2 instead. Some write-ups suggest it. It costs more performance than the Base64 flag, and it stops the JVM starting on ARM.
  • Container images. The bizhubaustralia/skyve-wildfly images, both the standard image and the database variants, now set the flag. The 39.0.1.Final, 39 and latest tags were republished with it on 19 November 2026. They still run JDK 21.0.10, because the upstream WildFly images haven't moved to a fixed JDK yet, so the flag is what protects them. We will rebuild them when the upstream images are updated. The flag is added to standalone.conf after the default JAVA_OPTS, so it still applies if your deployment sets its own JAVA_OPTS. Rebuild your application image on the updated image and redeploy. No change to Skyve or your application is needed. Images for older WildFly versions will not be updated. If you use one, move to the 39 image, or add the flag yourself as described above until you can. When you move, remove any ENTRYPOINT [ "entrypoint.sh" ] line from your Dockerfile, because the 39 images no longer include that script. Do the same if you build on your own WildFly image.
  • Upgrade the JDK. Fixed builds are 17.0.21.1, 21.0.13.1 and 25.0.5.1. Oracle, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft and the Red Hat build of OpenJDK have all released them. At the time of writing, Red Hat has not released fixed java-*-openjdk packages for Red Hat Enterprise Linux 8, 9 or 10, and the official eclipse-temurin Docker images are still on the October builds. If you get Java from either of those, keep the JVM flag in place until they update. Once you have upgraded, restart every JVM. A JDK that is installed but not yet running protects nothing.
  • Check your CPU. On Linux, grep -o avx512vbmi /proc/cpuinfo prints nothing if the CPU lacks the instruction set. Bear in mind that cloud and virtualised servers can move between hardware generations, so we still recommend the flag even if your current host isn't affected.
  • Review your own code. Search your project and its dependencies for Base64.getDecoder() and Base64.getUrlDecoder() used on request data. Pay particular attention to anything that runs before a user has logged in.
  • Review your authentication configuration. If you enabled SingleCustomerBasicAuthenticationFilter or Spring Basic authentication, confirm it is still needed.

Further Reading

We will update this advisory when the remaining JDK packages and images are fixed, and when we rebuild the Skyve WildFly images on a fixed JDK.

Need Help?

If you have questions about this advisory, please contact us via GitHub Discussions or Slack, or reach out to Biz Hub through your usual support channel.

Ben PetitosecurityComment