Follow

Security Advisory: CVE-2026-114938 ("Java4Shell") Update

Advisory ID: HC-SA-2026-001 Status: Under review / informational Last updated: 19 November 2026

Summary

Action: update the JDK that runs your Heirloom deployment to a fixed release. If you cannot update immediately, add -XX:-UseBASE64Intrinsics to the JVM startup options and restart.

CVE-2026-114938 is a memory-corruption flaw in the HotSpot JVM's hardware-accelerated Base64 decoder (java.util.Base64), used on x86-64 CPUs with AVX-512 VBMI. Crafted Base64 input can write past the end of a heap buffer. Depending on the application, this can crash the JVM, disclose memory, or allow unauthenticated remote code execution.

The flaw is in the JDK, not in Heirloom code, so the fix is a JDK update. It applies to every Java application on an affected JDK and CPU, including Heirloom products.

Are Heirloom products affected?

Heirloom products are exposed whenever they run on an affected JDK on an affected CPU. Heirloom products do not ship or embed a JVM; they run on the JDK in the customer's application server or container image, so exposure depends on that JDK and host.

Untrusted Base64 input: customers should assume this condition is met. Application servers and frameworks decode Base64 from requests (for example HTTP Basic authentication headers and SAML tokens) before any Heirloom code runs, often before the user is authenticated. [CONFIRM: state the result of the Heirloom source review, i.e. whether Heirloom products themselves pass request data to java.util.Base64.]

Heirloom-provided images and templates: [CONFIRM: if Heirloom publishes container images, Dockerfiles or deployment templates that pull a JDK, state whether they have been rebuilt on a fixed JDK and from which version. If none exist, say so.]

No Heirloom product update is required. The fix is entirely at the JDK layer.

Affected environments

An environment is affected when both of the following are true. If you are unsure, assume it is affected.

  • JDK version: OpenJDK 17.0.6 or later, or any 21, 25 or 27 release, before the vendor's fixed build. This includes Oracle Java SE, Eclipse Temurin, Azul Zulu, Amazon Corretto, Microsoft Build of OpenJDK, Red Hat OpenJDK, BellSoft Liberica, SAP SapMachine and Oracle GraalVM. Standard Java 8 and 11 are not affected, except Oracle Java SE 8 Enterprise Performance Pack and Azul Prime 8 and 11.
  • CPU: an x86-64 processor with AVX-512 VBMI, from Intel (Xeon Ice Lake and newer) or AMD (EPYC Zen 4 and newer). Many cloud instance types use these CPUs. ARM64 hosts (AWS Graviton, Ampere, Apple silicon) are not affected.

How to check (Linux):

java -version
grep -o -m1 avx512vbmi /proc/cpuinfo

If the second command prints avx512vbmi, the CPU is in scope. Virtual machines and containers report the host CPU's flags, so run it inside the VM or container.

Remediation: update the JDK

Updating to a fixed JDK build fully resolves the issue. Rebuild container images on the patched base image and restart every JVM.

Fixed builds as of 18 November 2026 (vendors are releasing on their own schedules; check your vendor's advisory for the latest):

JDK line Oracle Java SE Amazon Corretto Azul Zulu Temurin, Microsoft, Red Hat
17 17.0.21.1 17.0.21.1.2 November 2026 CSPU build Check vendor
21 21.0.13.1 21.0.13.1.2 November 2026 CSPU build [CONFIRM exact build number] Check vendor

Sources: Scala security advisory, Azul. Azul Prime users should move to 26.08.110.0 or 26.02.510.0.

Interim mitigations (if you cannot update immediately)

These reduce risk until the JDK is updated; they do not replace the update.

  1. Disable the vulnerable intrinsic. Add -XX:-UseBASE64Intrinsics to the JVM options of the application server or container, then restart the JVM. The JVM falls back to the plain Java decoder. This is a configuration change only, with no change to Heirloom applications. Base64-heavy workloads may run slightly slower. To apply it to every JVM on a host or container: export JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics". Confirm it took effect with java -XX:+PrintFlagsFinal -version | grep UseBASE64Intrinsics (expect false). Remove it once you are on a fixed JDK.
  2. Run on unaffected CPUs. Where your infrastructure allows, schedule workloads onto ARM64 hosts or x86-64 hosts without AVX-512 VBMI.
  3. Restrict access. Limit network access to application endpoints to trusted sources. For systems that cannot be updated or mitigated, CISA and the Canadian Cyber Centre recommend restricting access or taking them offline.

Some vendors also suggest -XX:UseAVX=2. We recommend the UseBASE64Intrinsics flag instead: it is narrower, and UseAVX is not recognised by ARM JVMs, which will fail to start with it.

Exploitation status and detection

As of 17 November 2026, no exploitation in the wild had been reported and the CVE was not in CISA's Known Exploited Vulnerabilities catalog. The researchers have withheld product-specific exploit code. CISA nonetheless urges immediate patching, and this section will be updated if the status changes.

Signs worth investigating on affected systems:

  • Unexpected JVM crashes, especially new hs_err_pid*.log files.
  • Malformed or unusually long Base64 values in HTTP Basic authentication headers, SAML artifacts or CSRF tokens in proxy, WAF or application logs.
  • Unexpected child processes started by the Java process.

Supported JDKs

Moving to a fixed JDK build is supported and recommended. Heirloom supports its products on OpenJDK-based 17 and 21 distributions, and the fixed builds are patch-level updates within those major versions. Customers on JDK 25 or 27 should update to the fixed build for that line, subject to Heirloom's support policy for those versions.

Contact

Customers who want help assessing a specific deployment should contact Heirloom Computing support. We can review your configuration and advise on the remediation path.

References

This advisory is provided for informational purposes and will be updated as vendors release fixed builds or the exploitation status changes.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk