Java4Shell (CVE-2026-114938): Reported Unauthenticated RCE in OpenJDK 17 Amid Oracle's November 2026 Java SE Patch Update
Oracle's November 17, 2026 Critical Security Patch Update includes 11 Java SE fixes, all for flaws that may be exploitable over a network without authentication. One of them, CVE-2026-114938, has been nicknamed Java4Shell. Early reports describe it as unauthenticated remote code execution caused by memory corruption in OpenJDK 17 (17.0.6 and later), rated 9.2 under CVSS 4.0. Calif says it discovered and reported the flaw, and it planned to publish technical details after Oracle released a patch. watchTowr cautioned that the technical details were still unconfirmed. Oracle has not confirmed the details or named the affected component. No exploitation or public proof-of-concept has been reported so far. This analysis is based on the article alone, since no web research was performed.
Entenda a falha
A vulnerabilidade
CVE-2026-114938, nicknamed Java4Shell, is reported as unauthenticated remote code execution caused by memory corruption in OpenJDK 17 (17.0.6 and later), rated 9.2 under CVSS 4.0 by early reports. Oracle has not confirmed the details or named the affected component. It is one of 11 Java SE fixes in the November 17, 2026 Critical Security Patch Update, all exploitable over a network without authentication. Oracle lists Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, GraalVM and JavaFX builds as affected; planned fixed builds include 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
Como funciona
The articles do not describe the vulnerable code path. They say only that the bug is memory corruption reachable over the network without authentication, and that running Java does not by itself make a service exploitable. Risk depends on whether attacker-controlled input can reach the vulnerable code, and Oracle has not said which component that is.
Por que é vulnerável
Early reports name memory corruption as the root cause, citing an advisory attributed to South Korea's National Cyber Security Center. If that scope holds, the flaw has been present since OpenJDK 17.0.6 shipped in January 2023. The articles do not explain why it went unnoticed or what the fix changes. The 9.2 CVSS 4.0 score may describe the same bug as Oracle's highest CVSS 3.1 score of 8.1, or a different one.
Como foi descoberta
Calif says it discovered and reported Java4Shell, writing on X that the vulnerability had leaked, and said it would publish technical details after Oracle released a patch. The flaw became public through early reports around Oracle's November 17, 2026 patch update. watchTowr acknowledged the reports but cautioned that the technical details were still unconfirmed. Oracle has not confirmed the details.
Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 14:15.
Detalhes técnicos
- Root cause reported as memory corruption. The early reports cite an advisory attributed to South Korea's National Cyber Security Center.
- If that scope holds, the flaw has existed since OpenJDK 17.0.6 shipped in January 2023.
- Oracle scores with CVSS 3.1, and its highest Java SE score this month is 8.1. The 9.2 figure may describe the same bug or a different one.
- Running Java does not by itself make a service exploitable. Risk depends on whether attacker-controlled input can reach the vulnerable code.
- Oracle lists Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1 as affected. It also lists GraalVM for JDK 17.0.21 and 21.0.13, GraalVM Enterprise 21.3.20.0.3, and JavaFX 21.0.13, 25.0.5 and 27.0.1.
- OpenJDK builds from other vendors (Eclipse Temurin, Amazon Corretto, Azul Zulu) follow their own schedules.
Remediação
- Apply the updates once fixed builds are available. Oracle's planned builds include 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
- No workaround has been published.
- Inventory every Java runtime, including bundled JDKs and container base images.
- Patch internet-facing Java services first.
- Watch each OpenJDK vendor's advisory for its fixed build number.
- Expect the risk to rise once Calif publishes its write-up.
Linha do tempo
-
Java4Shell (CVE-2026-114938): Reported Unauthenticated RCE in OpenJDK 17 Amid Oracle's November 2026 Java SE Patch Update
ler a análise desta fonte ocultar
Oracle's November 17, 2026 Critical Security Patch Update includes 11 Java SE fixes, all for flaws that may be exploitable over a network without authentication. One of them, CVE-2026-114938, has been nicknamed Java4Shell. Early reports describe it as unauthenticated remote code execution caused by memory corruption in OpenJDK 17 (17.0.6 and later), rated 9.2 under CVSS 4.0. Calif says it discovered and reported the flaw, and it planned to publish technical details after Oracle released a patch. watchTowr cautioned that the technical details were still unconfirmed. Oracle has not confirmed the details or named the affected component. No exploitation or public proof-of-concept has been reported so far. This analysis is based on the article alone, since no web research was performed.
Technical Details
- Root cause reported as memory corruption. The early reports cite an advisory attributed to South Korea's National Cyber Security Center.
- If that scope holds, the flaw has existed since OpenJDK 17.0.6 shipped in January 2023.
- Oracle scores with CVSS 3.1, and its highest Java SE score this month is 8.1. The 9.2 figure may describe the same bug or a different one.
- Running Java does not by itself make a service exploitable. Risk depends on whether attacker-controlled input can reach the vulnerable code.
- Oracle lists Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1 as affected. It also lists GraalVM for JDK 17.0.21 and 21.0.13, GraalVM Enterprise 21.3.20.0.3, and JavaFX 21.0.13, 25.0.5 and 27.0.1.
- OpenJDK builds from other vendors (Eclipse Temurin, Amazon Corretto, Azul Zulu) follow their own schedules.
Remediation
- Apply the updates once fixed builds are available. Oracle's planned builds include 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
- No workaround has been published.
- Inventory every Java runtime, including bundled JDKs and container base images.
- Patch internet-facing Java services first.
- Watch each OpenJDK vendor's advisory for its fixed build number.
- Expect the risk to rise once Calif publishes its write-up.