Skip to main content

Java4Shell Security Advisory (CVE-2026-114938): Affected Java Systems and Urgent Actions

Critical Java4Shell (CVE-2026-114938) advisory: affected Oracle Java releases, AVX-512 exposure requirements, patch versions and an actionable enterprise response checklist.

17 November 2026 | ZebraByte Security Advisory. Researchers have disclosed Java4Shell (CVE-2026-114938), a critical vulnerability rated 9.2/10 under CVSS 4.0 in OpenJDK's optimised Base64 decoder. It can cause memory corruption and potentially remote code execution (RCE) under specific conditions. Oracle published security updates on 17 November.

Our recommendation: identify Java runtimes immediately, determine exposure using technical prerequisites and patch affected workloads, prioritising externally reachable services. Do not assume that every Java application is equally exploitable.

What is Java4Shell?

The flaw affects a native optimisation in the Java Virtual Machine that accelerates Base64 decoding. Base64 is widespread in web applications, authentication mechanisms, tokens and data exchange. Crafted input may trigger an out-of-bounds write in the affected native decoder when the required JVM and hardware conditions are met.

Calif.io reports unauthenticated RCE demonstrations against certain Java applications. Independent Datadog analysis highlights that denial of service is more readily achieved, while reliable RCE depends on additional application-specific exploitation. There is no universal exploit that automatically compromises all Java servers.

Exposure criteria and priority systems

Three elements matter: an affected Java runtime, an x86-64 processor supporting AVX-512 VBMI, and an application path that passes attacker-controlled data to the vulnerable Base64 decoder. Native ARM64 runtimes are not affected by this specific execution path. Missing one of these conditions changes the assessment for this CVE.

Prioritise public authentication gateways and APIs, enterprise management platforms, artifact repositories, containerised services and externally reachable applications. The original researchers reported tests involving Keycloak, Jira, Confluence, Jenkins and Artifactory. These findings must not be treated as proof that every release or installation of each named product is vulnerable.

Oracle Java versions requiring remediation

The reported first fixed Oracle Java SE builds are Java 17.0.21.1, Java 21.0.13.1, Java 25.0.5.1 and Java 27.0.1.1. For Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK and other downstream vendors, consult the vendor-specific patched build advisory. Standard Java 8 and 11 lines do not contain this particular defect, though they still require updates for unrelated security issues. Oracle separately identifies an affected Java 8 Enterprise Performance Pack build.

Immediate response checklist for IT teams

1. Inventory JDKs, JREs and JVMs on hosts, virtual machines, inside container images and bundled with applications. 'java -version' only identifies one executable on the current PATH and must not be used as a complete inventory.

2. Prioritise internet-facing workloads and check CPU support. On Linux, 'grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo' provides an initial indication of relevant AVX-512 VBMI support. Correlate this with the actual Java version and the application's data flow.

3. Apply the patched runtime supplied by your Java vendor. Rebuild container images and restart affected services to ensure the running workload uses the fixed build. Test critical application workflows.

4. If patching cannot be completed immediately, restrict inbound access using firewalls, trusted-source allowlists or VPNs. JVM options '-XX:-UseBASE64Intrinsics' or '-XX:UseAVX=2' (x86-64 only) can disable the affected acceleration path based on published tests. Validate these mitigations in your environment and do not treat them as permanent replacements for patching.

5. Monitor unexpected JVM crashes, anomalous decode errors, unplanned child processes and suspicious outbound traffic. Preserve logs and forensic evidence if indicators justify incident investigation.

What should leadership receive?

A useful executive update should state the number of Java assets inventoried, systems meeting the technical exposure criteria, externally reachable services, confirmed patched builds, temporary restrictions and outstanding exceptions. Avoid unsupported statements such as 'all Java systems are compromised' or 'our WAF makes the vulnerability impossible'.

ZebraByte's security position

We recommend evidence-led exposure assessment, verifiable remediation and continuous monitoring. This advisory is informational and does not claim that any particular customer's infrastructure has already been assessed or declared safe. At the time of the 17 November disclosure, widespread in-the-wild exploitation had not been publicly confirmed; that assessment may change.

References

Original Calif.io disclosure: https://calif.io/java4shell/

Independent Datadog technical analysis: https://securitylabs.datadoghq.com/articles/java4shell-remote-code-execution-in-openjdk-cve-2026-114938/

Oracle's official advisory: https://www.oracle.com/security-alerts/cspunov2026.html

Published: 17 November 2026. Consult current vendor advisories for build-specific updates.

ZebraByte editorial profile

Andreea Marinescu

Cybersecurity and infrastructure

Fictional ZebraByte editorial profile; AI-generated portrait. Not a real person or employee.