TL;DR
- Java4Shell (CVE-2026-114938), a reported unauthenticated remote code execution flaw has been reported in Java 17, 21, 25 and 27 releases before the patched builds below, rated 9.2 under CVSS 4.0.
- Oracle released patched builds on November 17, 2026. Java SE 8 and 11 are not affected by this CVE.
- Update every Java line you run to the patched build in the table below,
- To find out if you are affected, click "Am I affected?" on the Aikido dashboard.
Which Java versions and builds are affected?
All Java builds Oracle lists as affected, with the patched builds from Oracle's November 17, 2026 release notes.
- Reports tie CVE-2026-114938 to the Java 17 line only, affecting all versions before 17.0.21.1. Oracle's list covers its whole November update, so treat every Java line you run as in scope.
- Oracle’s November update also fixes other Java flaws, including in Java SE 8 and 11, so keep every Java line you run up to date.
Java builds to check:
- Oracle Java SE (JDK and JRE)
- Oracle GraalVM for JDK and GraalVM Enterprise Edition
- Oracle JavaFX
- OpenJDK builds from other vendors, such as Eclipse Temurin, Amazon Corretto, Azul Zulu, the Microsoft Build of OpenJDK and the Red Hat build of OpenJDK
- Linux distribution packages such as openjdk-17
- JDKs bundled inside applications and container base images
How to fix Java4Shell
- Update to the patched build for your Java line. Use the table above.
- Use your vendor's fixed build. If you run Temurin, Corretto, Zulu or a distribution package, wait for that vendor's fixed version, which may carry a different build number.
- Not sure where you run Java? See the next section.
Am I affected by Java4Shell?
- You are in scope if you run Java 17, 21, 25 or 27 before the fixed version in the table above. That includes bundled JDKs and container base images.
- To find out if you are affected, click "Am I affected?" on the Aikido home page. It checks your environment for this vulnerability, so you do not need to track down every Java runtime by hand.
- Start with internet-facing services. Anything reachable from outside is the likeliest to be hit once details are public.
What is Java4Shell (CVE-2026-114938)?
Java4Shell is the name given to CVE-2026-114938. Early reports describe it as an unauthenticated remote code execution flaw in all Java 17 versions before 17.0.21.1, rated 9.2 (Critical) under CVSS 4.0. Oracle scores Java flaws under CVSS 3.1, where its highest Java SE score this month is 8.1, so the two figures may describe different issues. For reference, 9.2 under CVSS 4.0 is the same score PHP2Shell carries.
Further technical details are expected after Oracle's patch release. Until then, the vulnerable component and the conditions for exploitation are not public. We will update this post when they are.
Is Java4Shell being exploited?
As of November 17, we have seen no reports of exploitation in the wild. Technical details are due later today, and exploitation can follow quickly once details are public, so patch now. We will update this post if that changes.
FAQ
What is Java4Shell? The name given to CVE-2026-114938, a reported unauthenticated remote code execution flaw in Java 17 rated 9.2 under CVSS 4.0.
Which Java versions are affected? Java 17, 21, 25 and 27 releases before 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Java SE 8 and 11 are not affected by this CVE.
Has Oracle released a patch? Yes. Oracle released patched builds on November 17, 2026. They are listed in the table above. OpenJDK vendors ship on their own schedules.
Is Java4Shell being exploited? We have seen no reports of exploitation as of November 17.
Is there a workaround? None has been published that we are aware of. Patching is the fix.
How do I know if I am affected? Click "Am I affected?" on the Aikido dashboard.
