By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
18px_cookie
e-remove
Blog

Java4Shell: Unauthenticated RCE Reported in OpenJDK 17 (CVE-2026-114938)

CVE-2026-114938, nicknamed Java4Shell, is a reported unauthenticated remote code execution flaw in OpenJDK 17.0.6 and every later Java 17 update. Early reports score it 9.2 under CVSS 4.0 and describe the root cause as memory corruption. Calif says it discovered and reported the bug, that details leaked before coordinated disclosure, and that it will publish a technical writeup by 1 PM Pacific today, after Oracle ships a patch.

Written by
Peyton Kennedy
Peyton Kennedy
Published on
November 17, 2026
Updated on
November 17, 2026

As of this writing, the CVE record is still reserved. No vendor has published an advisory naming the vulnerable component or a fixed build tied to this CVE, and nobody has reported exploitation in the wild. Oracle's November 2026 Critical Security Patch Update (CSPU), scheduled for today, contains 11 Java SE fixes. Oracle has not said whether this CVE is one of them.

If you run Java 17 in production, inventory every live JVM now so you can patch within hours of fixed builds appearing. We will update this post when Oracle's risk matrix, the OpenJDK Vulnerability Group advisory and Calif's writeup are public.

Affected versions

Only the Java 17 line has been publicly tied to CVE-2026-114938. Oracle's CSPU list covers all 11 of its Java SE fixes and is not a per-CVE scope.

ProductVersions listedFixed build
OpenJDK 17 (upstream and downstream builds)17.0.6 and laterNot published
Oracle Java SE 1717.0.2117.0.21.1 reportedly scheduled
Oracle Java SE 2121.0.1321.0.13.1 reportedly scheduled
Oracle Java SE 8, 11, 25, 278u511, 8u511-perf, 11.0.33, 25.0.5, 27.0.1Not published
Oracle GraalVM for JDK17.0.21, 21.0.13Not published
Oracle GraalVM Enterprise Edition21.3.20.0.3Not published
Oracle JavaFX21.0.13, 25.0.5, 27.0.1Not published

Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat build of OpenJDK and the distro openjdk-17 packages ship on their own schedules and version labels. Read each vendor's fixed build from its own advisory. Do not infer it from Oracle's numbering.

What's happening

Most of what is circulating about Java4Shell is secondhand, and the vendor record is empty. The table separates what is reported from what is confirmed.

ClaimStatusBasis
Unauthenticated RCE exists in OpenJDK 17.0.6 and laterReportedAdvisory attributed to South Korea's National Cyber Security Center (NCSC), cited secondhand; Calif's public claim of discovery
CVSS 4.0 score of 9.2ReportedKorean-language reporting. No vector string has been published
Vulnerable componentNot disclosedNo vendor advisory or researcher writeup has named it
Fixed in Oracle's November CSPUUnconfirmedOracle's advisory page still showed the pre-release announcement when I checked
Exploited in the wildNone reportedNot in CISA KEV, which is expected while the record is reserved
Public proof of conceptNone publishedCalif's writeup was not yet on its research page when I checked

Timeline

DateEvent
Nov 17, 2026Calif posts that it discovered and reported Java4Shell, that the bug leaked, and that technical details will follow Oracle's patch
Nov 17, 2026Oracle's November CSPU is scheduled: 11 Java SE fixes, all described as remotely exploitable without authentication, highest CVSS 3.1 score 8.1
Nov 16 to 17, 2026NCSC advisory to Korean public institutions flags an unauthenticated Java RCE and asks them to prepare for updates. Reports differ on whether it was dated the 16th or 17th
Jan 2023OpenJDK 17.0.6 ships, the first build in the reported affected range

The Korean reporting places disclosure at 6 AM KST on November 18, which is 1 PM Pacific on November 17. That lines up with Calif's stated publication time.

Severity in context

The reported 9.2 is a CVSS 4.0 score. Oracle scores Java SE under CVSS 3.1, and its highest Java SE score in the November CSPU is 8.1. No vector string for CVE-2026-114938 and no Oracle risk matrix have been published, so the two numbers cannot yet be compared or tied to the same flaw.

For context, last month's PHP2Shell, another leaked runtime RCE scored 9.2 under CVSS 4.0, has since been added to CISA KEV. Calif has said its Java4Shell writeup will publish after Oracle's patch.

What to do

  1. Find the JVM each service actually runs. java -version reports whatever is on the shell's path, and bundled applications often ship their own runtime. Check the live process instead:
ps -eo pid,args | grep '[j]ava' readlink -f /proc//exe jcmd VM.version

Run jcmd as the same user as the target process. For containers, check the base image in every Dockerfile and pipeline so the next deploy does not reintroduce an old JDK.

  1. Rank internet-facing services first. ss -lntp shows listening sockets, but a port list does not prove reachability. Trace each path through load balancers, security groups and proxies, and restrict admin interfaces to management networks.
  2. Patch the runtime as soon as fixed builds appear. Oracle JDK and GraalVM customers get fixes through the November CSPU, with 17.0.21.1 reportedly the Java 17 replacement. Downstream distributions publish their own builds. Rebuild and redeploy container images, restart every Java process, and confirm the running build with jcmd. The installed package version alone does not prove the fix is live.
  3. Watch the primary sources. Oracle's CSPU risk matrix, the OpenJDK Vulnerability Group advisory page, Calif's writeup and CISA KEV will each change the picture today. We will fold them into this post as they publish.

No vendor has published a workaround or configuration change for CVE-2026-114938.

‍

Actions for Endor Labs customers

Java4Shell sits in the Java runtime. Your pom.xml or build.gradle does not declare the JDK, so dependency scanning of application manifests will not surface it.

Use container scanning to find images that carry OpenJDK 17 packages in the reported range. Container reachability adds evidence about whether the affected OS package is used at runtime. That helps order the work. It does not tell you whether the vulnerable decode path is reachable, so we recommend upgrading affected Java 17 runtimes regardless of reachability status.

When the JDK comes from a base image, base image remediation compares your current image with a refreshed build, the next version and the latest version. Once your JDK vendor publishes its fixed build, confirm the candidate image includes it, then rebuild, redeploy and rescan.

Resources

‍

‍