Description

On November 17, 2026, Oracle released its November 2026 Critical Security Patch Update, which addresses CVE-2026-114938 in the Compiler component (HotSpot) of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition.
The OpenJDK Vulnerability Group published its advisory for OpenJDK 17, 21, 25, and 27 on the same day.
Oracle rates the vulnerability as difficult to exploit, but exploitable over the network by an unauthenticated attacker who supplies data to the affected APIs, for example through a web service.
According to Oracle, a successful attack can result in takeover of the Java runtime.

Oracle does not publish technical details.
Calif, the research team that Oracle credits for the report, named the flaw "Java4Shell" and published a technical write-up.
According to that write-up, it is a heap-based buffer overflow (CWE-122) in the AVX-512 accelerated Base64 decoder that HotSpot uses on x86-64 processors once java.util.Base64 decoding is JIT-compiled.
A Base64 string that ends in a padded tail shorter than one 4-character block (for example, a stray =) makes the decoder compute a negative output length and store a full 64-byte block, up to 63 bytes past the end of the destination array on the Java heap.
Java rejects the input with an IllegalArgumentException only after the write has happened.
Because applications decode Base64 from Authorization headers, tokens, and file uploads, the vulnerable code is often reachable before authentication.

Calif reports remote code execution (RCE) without authentication against default configurations of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate, and with authentication against Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.
These results are not confirmed by Oracle; Calif published a proof of concept that only triggers the overflow and is withholding the product-specific exploit chains.
Calif scores the flaw 9.2 under CVSS v4.0; this advisory follows Oracle's rating.
At the time of writing (November 18, 2026), no exploitation in the wild has been reported and the CVE is not listed in the CISA KEV catalog.
Independent teams have reproduced the overflow, and VulnCheck states that it supplies a full RCE exploit to its customers, while it does not expect the flaw to be easily or widely exploitable.

  • Severity: High
  • CVSS Score: 8.1 (CVSS v3.1, rated by Oracle, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
  • CWE-122: Heap-based Buffer Overflow

Scope of Impact

The flaw is in the JVM itself, not in application code.
Affected versions and patches according to Oracle and the OpenJDK Vulnerability Group:

  • Oracle Java SE: 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3, and the Java 8 Enterprise Performance Pack 8u511b33-perf are affected; upgrade to 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, or 8u513-perf.
  • Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3 are affected; apply the November 2026 Critical Security Patch Update release.
  • Oracle GraalVM Enterprise Edition: 21.3.20.0.3 is affected; apply the November 2026 Critical Security Patch Update release.
  • OpenJDK: 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3, and earlier are affected; fixed in 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1 (change JDK-8393212).
  • Earlier and unsupported versions: Oracle states that earlier versions of affected releases are likely also affected and that releases outside Premier or Extended Support are not tested.
  • Not listed as affected: Standard Java 8 and Java 11.

Other distributions built from OpenJDK carry the same code and release fixes on their own schedule:

  • Amazon Corretto: Upgrade to 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, or 27.0.1.1.4.
  • Eclipse Temurin, Azul Zulu, Microsoft Build of OpenJDK, Red Hat build of OpenJDK, BellSoft Liberica, SAP SapMachine, and Linux distribution packages: Follow each vendor's advisory; at the time of writing, Eclipse Temurin and Debian had not yet published a fixed build.
  • Bundled runtimes: JDKs shipped inside products and container images must be updated separately from the operating system packages.

Oracle does not describe exploitation preconditions beyond high attack complexity.
According to Calif and independent analyses (Semgrep, Endor Labs, Upwind), a JVM is exposed only when all of the following conditions hold:

  • Runtime: HotSpot JVM version 17.0.6 or later (including 21, 25, and 27) without the fix.
  • CPU: x86-64 processor that exposes AVX-512 VBMI and AVX-512 BW to the JVM, such as Intel Xeon Ice Lake or later and AMD Zen 4 or later.
  • JVM settings: Base64 intrinsics and the C2 JIT compiler enabled and UseAVX set to 3, which are the defaults on such processors.
  • Input: Untrusted data reaches Base64.getDecoder() or Base64.getUrlDecoder().

By the same analyses, OpenJDK 17.0.0 to 17.0.5, ARM64 systems, x86-64 processors without AVX-512 VBMI, and non-HotSpot JVMs such as Eclipse OpenJ9 are not exposed.
End-of-life feature releases (18 to 20, 22 to 24, and 26) contain the same code, receive no upstream patches, and must be moved to a supported release line.

Note: On virtual machines and containers, the JVM sees the CPU features that the hypervisor exposes, so run the check inside the instance that hosts the workload.

# The CPU condition holds only if all four flags are listed
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

# Version and effective flags of a running JVM
jcmd <PID> VM.version
jcmd <PID> VM.flags -all | grep -E 'UseBASE64Intrinsics|UseAVX'

Impact

Oracle rates the impact on confidentiality, integrity, and availability as High.
Successful exploitation of the vulnerability can lead to:

  • Takeover of the Java runtime by an unauthenticated network attacker (Oracle); in practice, code execution in the JVM process with the privileges of the affected service.
  • Heap memory disclosure in server responses (session tokens, credentials, and other users' data), which Calif calls "JavaBleed" and uses as a step toward code execution.
  • Denial of service: a failed exploitation attempt can crash the JVM (Calif), and a simple burst of malformed requests reliably brought a service down in VulnCheck's testing.
  • Compromise of identity, CI/CD, and artifact systems (Keycloak, PingFederate, Jenkins, Artifactory, Jira, Confluence, according to Calif), followed by credential theft, supply chain tampering, and lateral movement to related infrastructure.
  • Client-side exposure: Calif also reports an exploit against Java programs that open TLS connections to a malicious server, so services that only make outbound connections are in scope.

Mitigation

  • Inventory every Java runtime: OS packages, tarball installs, container base images, and JDKs bundled inside products (Jenkins, Keycloak, Elasticsearch, and similar software often ship their own). Check the runtime of the running process, not only the installed package.
  • Upgrade each runtime to the fixed build for its release line as soon as possible, then restart every Java process and rebuild and redeploy container images (including base images). Neither Oracle nor OpenJDK lists a workaround specific to this vulnerability; upgrading is the required remediation.
  • Until the patch is applied, Oracle's general guidance is to reduce risk by blocking the network protocols an attack requires. Prioritize internet-facing services and identity, CI/CD, and artifact systems, and restrict access to their login and admin interfaces. Request buffering at a reverse proxy does not reliably block exploitation; treat proxy and WAF controls as risk reduction only.
  • Where a fixed build is not yet available or cannot be deployed immediately, Calif and independent testing (VulnCheck, Upwind) report that starting the JVM with -XX:-UseBASE64Intrinsics stops the overflow. This flag is not validated by Oracle. It is accepted on every architecture and disables the accelerated Base64 code, at the cost of slower Base64 processing. Set it in the service's JVM options or in JAVA_TOOL_OPTIONS, restart the process (recreate containers), and remove it after upgrading.
  • -XX:UseAVX=2 is an alternative for x86-64 hosts only: it turns off all AVX-512 code in the JVM, and ARM64 JVMs do not recognize the option and fail to start. Do not use -XX:DisableIntrinsic=_base64_decodeBlock on its own; it is a diagnostic option, and the JVM refuses to start unless -XX:+UnlockDiagnosticVMOptions is set before it.
  • Monitor for exploitation attempts: bursts of IllegalArgumentException from java.util.Base64$Decoder, Base64 values in headers or tokens that end in = with a length that is not a multiple of 4, unexplained JVM crashes or restarts (hs_err_pid*.log), and Java processes that spawn a shell or open new outbound connections. These signals are heuristics and do not prove compromise or safety.
  • To find exposed JVMs across a fleet, Semgrep publishes read-only detection scripts for Linux, macOS, and Windows hosts, with wrappers for Ansible, SSH, Kubernetes, Azure, AWS, and GCP. They probe each JVM for the conditions above and exit with 0 (not impacted), 1 (impacted), or 2 (unknown). Review third-party scripts before running them with root privileges. At the time of writing, they compare only the first three version components and still flag a patched build such as 17.0.21.1 as impacted, so confirm the full version string with java -version after upgrading.

Run the host detector on Linux or macOS as follows:

git clone https://github.com/semgrep/detection-scripts.git
cd detection-scripts/CVE-2026-114938
sudo ./linux/detect-jdk-8392044.sh

Use the following prompt with an AI agent that can access your infrastructure to run a read-only assessment. Give the agent read-only credentials, because the prompt alone does not stop it from making changes, and review its results before acting on them.

Read-only assessment: are my systems affected by CVE-2026-114938 (Java4Shell)? Details and fixed builds: https://greennode.ai/security-advisories/java4shell. Do not exploit, change, or restart anything.

For every running JVM (hosts, GreenNode vServer instances, VKS and other Kubernetes workloads, container images, bundled JDKs), record:
- Vendor, implementation, full running version (jcmd <pid> VM.version), and installed package version
- CPU flags inside the instance: avx512f, avx512bw, avx512vbmi, bmi2 (/proc/cpuinfo)
- UseBASE64Intrinsics and UseAVX (jcmd <pid> VM.flags -all)
- Internet reachability (public or floating IP, load balancer, ingress)

Exposed = unpatched affected build (HotSpot 17.0.6 and later, Oracle Java 8 Enterprise Performance Pack) on x86-64 with all four CPU flags, UseBASE64Intrinsics on, and UseAVX=3. Mitigated = -XX:-UseBASE64Intrinsics or UseAVX ≤ 2. Fixed = running a patched build (Oracle/OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, 8u513-perf; other vendors per their advisory).

Return a table: system | application | Java vendor | running version | installed version | CPU flags | JVM flags | Internet-facing | status (exposed, not exposed, mitigated, fixed, unknown) | next action. Every unpatched JVM still needs the upgrade. List what you could not assess and the access needed.

References