Java4Shell: remote code execution in OpenJDKPatch

CVE-2026-114938

A reported out-of-bounds write in OpenJDK, tracked as Java4Shell, could let an unauthenticated attacker run code in Java applications.

Zuletzt geprüft

Aktualisierungen

  1. Oracle released patched Java SE builds (opens in new tab) in its November update, and Calif disclosed Java4Shell (CVE-2026-114938).

Übersicht

Details

Calif discovered and reported CVE-2026-114938, which it calls Java4Shell. Datadog Security Labs describes it as an out-of-bounds write in OpenJDK, a flaw in the Java runtime itself rather than in a third-party library. According to Datadog, the bug is reached before an application can reject the input, so the application's own validation does not protect it.

Early reports name OpenJDK 17.0.6 and later as affected and rate the flaw 9.2 under CVSS 4.0. Oracle scores Java flaws under CVSS 3.1, and its highest Java SE score in the November update is 8.1; Aikido notes that the two figures may describe different issues.

As of November 17, the vulnerable component and the conditions for exploitation are not public, and the CVE record has not been published. Calif has said it will publish technical details after Oracle's patch release.

Risiko

An unauthenticated attacker may be able to run code in a Java application before it can reject the input. Aikido had seen no reports of exploitation as of November 17.

Betroffene Deployments

Oracle lists Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, GraalVM for JDK 17.0.21 and 21.0.13, and GraalVM Enterprise Edition 21.3.20.0.3 as affected by its November update. OpenJDK builds from other vendors, distribution packages, and JDKs bundled in applications or container images can be affected too.

Empfohlene Maßnahme

Update every Java runtime to Oracle's November 17 build or your vendor's fixed release, starting with Internet-facing services. Then verify the updated version is running.

  1. Find every Java runtime you run, including JDKs bundled in applications, distribution packages such as openjdk-17, and container base images. Run java -version for each one, and check the version the running JVM reports, not only the installed package.

  2. Update Oracle Java SE to the patched build for each line: 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1.

  3. For Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft, Red Hat or distribution builds, install that vendor's fixed release when it is available. Its build number may differ from Oracle's.

  4. Restart each updated service, because upgrading the package does not replace a JVM that is already running. Then check that each process reports the patched build, for example with jcmd <pid> VM.version.

Verwenden Sie diese Eingabeaufforderung mit einem Agenten, der Ihre Infrastruktur prüfen kann.

Assess whether the systems available to you are affected by CVE-2026-114938 (Java4Shell), a reported remote code execution flaw in OpenJDK. Perform a read-only assessment within your authorized access. Do not attempt exploitation, change systems or restart services.

1. Check Oracle's November 2026 Critical Security Patch Update (https://www.oracle.com/security-alerts/cspunov2026.html), the CVE record (https://www.cve.org/CVERecord?id=CVE-2026-114938) and each OpenJDK vendor's advisory for affected and fixed builds. Cite sources and retrieval dates, and note whether the CVE record is published.

2. Inventory accessible hosts, container images and applications that run Java, including JDKs bundled in applications. For each, record the Java vendor, the full version string of the running JVM (java -version, or jcmd <pid> VM.version for a running process), the installed package version, and whether the process started after the package was installed.

3. Note whether each Java service is reachable from the Internet.

Return a concise summary and a table: host or image | application | Java vendor | running version | installed version | Internet-facing | assessment (affected, fixed or unknown) | evidence | next action. Separate an installed fix from a running fix. List systems you could not assess and the access needed.

Find more information and resources at https://radar.cloudflare.com/zero-wire/java4shell

Evidence and sources

CVE record

As of November 17, the CVE record is not published, so the CVSS 4.0 score of 9.2 comes from early reports, not from the record.

Security research

Datadog describes the out-of-bounds write. Aikido lists the patched build for each Java line and notes the CVSS mismatch.