News and Notes from the Makers of Nexus | Sonatype Blog

Critical OpenJDK RCE CVE-2026-114938: What to Know

Written by Sonatype Research Team | November 17, 2026

TL;DR

  • Calif disclosed Java4Shell, tracked as CVE-2026-114938, as an unauthenticated remote code execution vulnerability in OpenJDK.

  • The flaw is in the Java runtime's Base64 decoding path, not a third-party library. Reachability depends on the runtime build, processor, and whether an application decodes untrusted Base64 data.

  • Oracle released updated Java builds as part of its November 2026 security update, but its pre-release notice does not map those Java fixes to this CVE by name.

  • Finding exposure requires checking runtimes on hosts and in container images. Project dependency scans alone will not identify every affected system.

  • For the current advisory and response guidance, see our Security Event page for the Critical OpenJDK Vulnerability.

A critical OpenJDK vulnerability, tracked as CVE-2026-114938, can allow an attacker to inject and remotely execute arbitrary code without authentication or user interaction. Calif calls the vulnerability Java4Shell.

The disclosure coincided with Oracle's Java security update on November 17, 2026. That timing has raised questions about which Oracle builds address Java4Shell and what organizations should check.

Teams need to identify vulnerable runtimes across their environments, prioritize network-accessible systems, and apply the patched OpenJDK build through the appropriate vendor.

Java4Shell Is a Runtime Vulnerability, Not a Library Flaw

Java4Shell is a memory corruption vulnerability in the Java runtime itself, not in a third-party library or framework. Because the flaw sits in the runtime, project dependency scans will not identify every affected installation.

Base64 decoding is common in applications that receive data over a network. Our research indicates that a Java 17 application could, in principle, be reachable when it decodes Base64 data from an untrusted source on an affected runtime build and processor.

That does not mean every Java application is exposed in the same way. The runtime build and processor matter, as does whether untrusted input can reach the decoder. The vulnerability is described as pre-authentication, because an attacker may be able to supply that input before logging in or interacting with the application.

Third-party analysis has also reported affected Java versions beyond Java 17. Upwind says it reproduced the memory corruption in tests on Java 17, 21, and 25, and identified Java 27 through code analysis. These are research findings, not a vendor's final affected-version list. Organizations should use vendor guidance to confirm the status of each runtime they operate.

Oracle's November Update Does Not Define the CVE’s Full Scope

Oracle released updated Java builds as part of its November 17 security update. Its November security notice lists 11 Java SE security fixes, all described as remotely exploitable without authentication, with a maximum CVSS 3.1 score of 8.1. Oracle also lists builds for Java SE 8, 11, 17, 21, 25, and 27, along with versions of GraalVM and JavaFX.

The notice is a pre-release announcement and does not identify the 11 issues by CVE. It therefore does not establish which update addresses Java4Shell. The Java versions Oracle lists as affected should not be treated as the confirmed affected-version range for this CVE.

Early coverage reports a 9.2 score for Java4Shell under CVSS 4.0. Oracle reports a maximum score of 8.1 under CVSS 3.1 for its Java SE fixes. Those scores use different CVSS versions and refer to different sets of vulnerabilities. They are not competing scores for the same confirmed issue.

Patch Confirmed Systems and Reduce Exposure

Treat systems confirmed to run a vulnerable OpenJDK build as exposed until the patched runtime is installed. Apply the update supplied by the vendor or distribution responsible for that runtime. Build numbers can vary across distributions, so confirm the fixed version with the supplier rather than assuming a particular version string applies everywhere.

Replacing runtime files on a host does not update a JVM process that is already running. Restart affected services after updating. Rebuild container images using a patched base image, and update products that bundle their own Java runtime. Then verify that the deployed service is running the patched build.

If a product bundles the vulnerable runtime and has no direct upgrade path, contact its maintainers for an update. If no update is available, investigate an alternative component or a mitigating control while tracking the issue to resolution.

Calif’s recommendations describe two possible temporary mitigations: disabling the Base64 intrinsic or limiting AVX use to version 2. The AVX setting applies only to x86-64 hosts. OpenJDK on ARM does not recognize it and may fail to start. These controls are not replacements for a patched runtime. Test them for compatibility and performance impact, and follow the relevant vendor's guidance.

What Teams Should Do Now

Organizations should:

  • Inventory runtimes: Check the Java runtime used by each running service, including runtimes on hosts, in container images, and bundled with products. Record the build, vendor, processor, deployment location, and owner. Package inventories can help, but they do not replace checking the runtime a service actually uses.

  • Assess reachability: Check for the relevant AVX-512 processor support and whether the Java Base64 intrinsic is enabled. Identify which Java services listen for network connections.

  • Prioritize exposure: Start with internet-facing and other network-accessible systems, then review the rest of the environment.

  • Confirm and apply the fix: Check Oracle or the relevant OpenJDK supplier for the patched build that applies to each runtime. Restart affected services and rebuild images as needed.

  • Reduce interim risk: Restrict or monitor network access to confirmed vulnerable systems while updates are being applied. Test any temporary mitigation and follow vendor guidance.

Connect Vulnerability Intelligence to Runtime Inventory

Java4Shell is a reminder that vulnerability response depends on knowing what runs across the environment, including the runtimes beneath applications.

CVE-2026-114938 requires organizations to look beneath project dependencies and account for the runtime installed across their environments. Finding each vulnerable OpenJDK build, assigning an owner, and verifying the patch are essential steps in reducing exposure.

Check Sonatype Guide and the associated Security Event page, which contain current details and response guidance as organizations identify affected OpenJDK deployments and verify remediation.