NEWS

Oracle Patches 11 Java Flaws as Reported OpenJDK RCE 'Java4Shell' Emerges

Oracle's Nov 17 update fixes 11 remotely exploitable Java SE bugs. A reported OpenJDK 17+ RCE, CVE-2026-114938, is not confirmed to be among them.

Dylan H.

News Desk

November 17, 2026
2 min read
Oracle Patches 11 Java Flaws as Reported OpenJDK RCE 'Java4Shell' Emerges

What happened

Oracle released security patches on November 17, 2026 for 11 Java SE vulnerabilities, all of which may be exploitable remotely without authentication. Separately, researchers have reported a potentially critical remote code execution flaw in OpenJDK, tracked as CVE-2026-114938 and nicknamed "Java4Shell".

Oracle's update

The affected builds are Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1. For Java 11, the patched build is 11.0.33.1. Oracle has not yet disclosed CVE identifiers, affected components or individual impact for the 11 fixes.

The reported OpenJDK flaw

ItemReported detail
CVECVE-2026-114938
NicknameJava4Shell (named by Calif)
AffectedOpenJDK 17.0.6 and later
SeverityCVSS 4.0 score of 9.2
CauseInteger underflow in the AVX-512 Base64 decoder, per Oligo
TriggerA crafted 65-byte input reportedly causes a 62-byte heap overflow
ExploitationNone reported in the wild as of Nov 17

Early reports cite a November 16 advisory attributed to South Korea's National Cyber Security Center. Calif said it would publish technical details after Oracle's patch release.

What is unconfirmed

  • No evidence links CVE-2026-114938 to Oracle's 11 scheduled fixes.
  • JFrog said no confirmed fixed version was publicly available at the time of writing.
  • Java 11 is not clearly affected by this specific CVE, and sources disagree on whether the Oracle builds had already shipped.
  1. Apply Oracle's November update to all Java SE deployments.
  2. Check your OpenJDK vendor's advisory for a CVE-2026-114938 fix. Don't assume the Oracle update covers it.
  3. Inventory Java 17 and later services that decode untrusted Base64 input, especially internet-facing ones.
  4. Watch for exploit details once Calif publishes them, and prioritize exposed services.

Sources