CVE-2026-114938
November 17, 2026
·
0
Minutes Read

652 Patch Oracle CSPU, Java4Shell

Advisory
Security Advisory
November 17, 2026
·
0
Minutes Read

652 Patch Oracle CSPU, Java4Shell

Advisory
Security Advisory
November 17, 2026
·
0
Minutes Read
Kudelski Security Team
Find out more
table of contents
Share on
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Summary

Oracle is releasing a Critical Security Patch Update (CSPU) on 17 November 2026 with 652 new security patches across its portfolio, including 11 patches for Oracle Java SE. Oracle states all 11 Java SE vulnerabilities may be remotely exploitable over a network without requiring authentication; the highest Java SE CVSS v3.1 base score is 8.1.

Separately, security researchers and news organisations are reporting an unauthenticated remote code execution vulnerability in Java 17, "Java4Shell" per security firm Calif, tracked as CVE-2026-114938, rated CVSS 4.0 9.2 (Critical) and said to affect OpenJDK 17.0.6 and later. Security firm watchTowr confirmed it is aware of public reports of an unauthenticated RCE in Java, and South Korean authorities have reportedly warned public bodies about a Java flaw allowing RCE without authentication.

Affected Systems and/or Applications

Java SE and related runtimes: Oracle lists Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, plus Oracle GraalVM Enterprise Edition 21.3.20.0.3, Oracle GraalVM for JDK 17.0.21 and 21.0.13, and Oracle JavaFX 21.0.13, 25.0.5 and 27.0.1.

Reported as affected by CVE-2026-114938: OpenJDK 17.0.6 and later Java 17 updates, a range covering roughly four years of builds, from January 2023. Because OpenJDK is redistributed by many vendors, fixes may arrive on different dates under different version names.

Java 17 remains a long-term support release widely used by banks, cloud providers and back-end systems, so exposure is likely to be broad. Inventory should cover the exact JVM, vendor and build in use, including Java inside containers, appliances and third-party applications.

The same CSPU also covers Oracle Database Server, APEX, REST Data Services, Communications, E-Business Suite, Fusion Middleware, Analytics, Hyperion, MySQL, PeopleSoft, Siebel, Supply Chain and VirtualBox, among others.

Consult the Oracle CSPU advisory for the complete product, component and version matrix.

Technical Details

Oracle’s "remotely exploitable without authentication" classification means the attack path can occur over a network and need not require valid credentials. It does not mean every Java installation is exploitable; applicability depends on the affected component being present and enabled, the vulnerable functionality being reachable over a network, configuration, and prerequisites that will appear in the final risk matrix.

CVE-2026-114938 remains largely undocumented. The identifier is reserved with no public technical detail, no named vulnerable component, no stated setup requirements, no proof of concept, no fixed build and no evidence of exploitation in the wild. The reported 9.2 score is CVSS 4.0, while Oracle's Java SE maximum of 8.1 is CVSS 3.1 — different scales, so the numbers are not directly comparable and neither confirms nor rules out a match.

Fix availability is unconfirmed. News reporting refers to builds 17.0.21.1 and 21.0.13.1 as reportedly scheduled, but Oracle's public JDK release-notes index currently lists 17.0.21.0.3 and 21.0.13.0.3 as the latest GA builds, with no mention of the reported .1 builds or of an emergency release.

Oracle's own position is that the CSPU information may change before the final advisory is published, and it recommends applying the patches as soon as possible given the threat posed by successful attack.

Mitigation

  • Inventory Java runtimes now. Record the executable path, vendor, full version and build for every JVM, including those inside containers, appliances and third-party products. Prioritise internet-facing Java 17 services until the picture is clearer.
  • Apply the CSPU promptly once available, prioritising exposed and business-critical systems, and restart affected Java processes so running instances load the corrected components.
  • Use vendor-supplied fixes. Obtain patches through My Oracle Support or from appliance, hosting and OpenJDK vendors, and confirm the correct fixed build rather than swapping in a standalone JDK.
  • Reduce unnecessary external exposure as an interim measure. Close internet access the business does not need and keep backups ready for rollback.
  • Watch for confirmation. Re-check Oracle's final advisory, the CVE record and your OpenJDK vendor's advisories for CVE identifiers, the affected component, exploit prerequisites and confirmed fixed builds. No workaround currently exists for CVE-2026-114938.

What the CFC is Doing

The CFC is monitoring the situation and analyzing the case to identify potential threat-hunting campaigns. This advisory will be updated if required.

References

‍

Related Post