TL;DR
- Calif has disclosed Java4Shell (CVE-2026-114938), a reported unauthenticated remote code execution flaw in Java 17, rated 9.2 under CVSS 4.0.
- Oracle released patched builds on November 17, 2026. It lists Java SE 8, 11, 17, 21, 25 and 27 as affected by its November update.
- 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?
Oracle's pre-release announcement lists these builds as affected by the vulnerabilities in the November update:
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 any Java line 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 Calif, the firm that discovered and reported the flaw, has given CVE-2026-114938. Early reports describe it as an unauthenticated remote code execution flaw in OpenJDK 17.0.6 and later, 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.
Calif has said it will publish technical details 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. Calif's 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 Calif has given 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? Reports name OpenJDK 17.0.6 and later. Oracle lists Java SE 8, 11, 17, 21, 25 and 27 as affected by its November update.
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 home page.