AI Security

Java4Shell: How to Check and Patch Your OpenJDK Runtime

Low Level's Java4Shell breakdown starts with a surprising place for a security flaw: Java's built-in Base64 decoder. The operational question is simpler than the code behind it: did you patch the JVM that actually serves traffic, or just the one your shell finds? A Java service can keep using an older runtime inside a container or bundled with an application even after the host's Java package is updated.

What to do first

For CVE-2026-114938, identify the Java vendor, build and architecture of each running service. Prioritize internet-facing services on affected x86-64 runtimes, move to your vendor's fixed build, and restart or replace every affected JVM. Verify the version on the replacement processes. CERT-EU advisory · Oracle release notes.

What Broke in HotSpot

Base64 represents binary data as text. In HotSpot, the just-in-time compiler can substitute an intrinsic: a specialized implementation of a familiar operation that uses CPU features to do the work faster. An application can call the normal java.util.Base64 API without knowing which implementation the runtime chose.

Here, an accelerated decoder can write beyond its output buffer on certain malformed input. That is memory corruption in the JVM's implementation, not a flaw in the Base64 format or a reason to assume every Java application is remotely exploitable. Oracle rates the issue 8.1 under CVSS 3.1, with high attack complexity and no authentication required in affected network-accessible scenarios. Red Hat rates it Critical and documents possible service crashes or code execution in affected applications. The labels come from different assessments; neither is a reason to delay patching an exposed service.

Which Deployments to Check

Three conditions matter: the Java build contains the flaw; the JVM can use the affected optimization; and untrusted data reaches that decoder. The standard HotSpot path described by CERT-EU applies to x86-64 environments exposing the required AVX-512 VBMI and related CPU features. ARM64 is not affected by that path. Check the CPU capabilities visible to the deployed JVM, not just the model name on the physical server: a VM, container deployment or mixed node pool may present a different environment.

Standard OpenJDK 8 and 11 lack this accelerated path, Red Hat says, but the major version alone can mislead. Oracle lists an affected Java 8 performance build, and Azul lists affected Platform Prime releases running Java 8 and 11. Identify the exact distribution before closing an inventory item.

Fixed Oracle Java SE Builds

These are the patch releases in Oracle's 17 November 2026 update, cross-checked against the CERT-EU affected-version table. For other distributions, OS packages and bundled JVMs, use the vendor's specific build or package advisory. A backported fix may not use Oracle's version suffix.

Java lineOracle Java SE fixed release
1717.0.21.1
2121.0.13.1
2525.0.5.1
2727.0.1.1
8, affected Oracle performance build only8u513

For GraalVM, use its product-specific guidance from Oracle's advisory. For Red Hat and Azul, use the Red Hat bulletin and the Azul fixed-build matrix. Owners of unsupported feature releases should move to a supported, patched line.

Patch and Verify the Running Service

  1. Inventory actual runtimes. Check service launchers, image manifests and vendor bundles. Record the Java vendor and build, image digest where relevant, architecture, service owner and exposure. Don't stop at the package manager.
  2. Prioritize exposed workloads. Update external services and shared identity or build infrastructure first. Authentication at the application boundary is not proof that untrusted input never reaches a decoder. Treat unclear inventory as something to resolve, not as a clean result.
  3. Roll out the patched build. Rebuild images that carry the affected runtime and replace running instances. For installed services, update the right runtime and restart the JVM. Confirm that no older replicas remain behind the load balancer.
  4. Check the new process. Use your runtime inventory or Oracle's documented jcmd <pid> VM.version from the appropriate host or container context, where available. java -version only describes the executable you invoked. Run normal health checks and watch service errors and restart rates. No exploit test is needed to verify the version.

A patched process doesn't tell you whether an older instance was compromised. If you already see unexplained JVM crashes or suspicious activity on a potentially exposed service, preserve relevant logs and escalate through your incident-response process. A crash alone is not evidence of exploitation.

If You Cannot Patch Immediately

Red Hat recommends -XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 without disabling unrelated AVX-512 optimizations. CERT-EU lists -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics. Follow the syntax your vendor documents for the exact runtime. The broader alternative, -XX:UseAVX=2, is for supported x86-64 JVMs only and can affect other vector-optimized code.

These are temporary startup changes, not fixes. Check that the service starts, verify the effective setting on the running JVM (for example, jcmd <pid> VM.flags -all where available), and watch performance. Retire the workaround after the fixed build is deployed and verified.

What AI Did in the Discovery

Calif researcher Quang Luong reported using Codex during the review. Low Level's account also notes that early suggestions needed filtering. The useful lesson is that AI can surface a candidate in hard-to-read runtime code; a human still has to determine whether it is real, document the evidence and get it to maintainers.

The earlier OpenJDK pull request highlighted in the video was a September proposal that closed without merging. That history is interesting, but it isn't a patch receipt. For an installed runtime, the authoritative evidence is the vendor's fixed-build advisory and the version reported by the process that's serving traffic.

Source Note: Editorial context: Low Level's java situation is insane (19 November 2026) and Calif's disclosure. Patch and mitigation guidance was checked against CERT-EU, Oracle, Red Hat and Azul on 19 November 2026. This defensive guide does not reproduce exploit instructions.

Share
X LinkedIn Reddit
Build Yours

Want a system
like this one?

Book a free 30-minute call. We map your situation, identify the highest-impact automation, and figure out if we are a fit.

Book Free 30-min Call