CVE-2026-114938: Critical Java 17 flaw reported as Oracle ships 652 patches

A critical remote code execution flaw reported in Java 17, tracked as CVE-2026-114938, has put server administrators on alert as Oracle released its November security update on Tuesday 17 November 2026.
Early reports describe the flaw as an unauthenticated remote code execution vulnerability affecting OpenJDK 17.0.6 and later Java 17 updates, rated 9.2 out of 10 under CVSS 4.0, which is the highest severity band. The reports cite an advisory dated 16 November attributed to South Korea's National Cyber Security Center, and point to memory corruption as the suspected root cause.
Important caveats remain. As of 17 November, the CVE record itself has not been published, no vendor has released a fixed build or a technical description, and no proof-of-concept code or sign of real-world exploitation has been reported. Oracle has also not tied the CVE identifier to any of the fixes in its November update, so the reported flaw and Oracle's patches should not be treated as confirmed to be the same thing.
What Oracle confirmed on 17 November
What is confirmed is the scale of Oracle's November 2026 Critical Security Patch Update. Oracle released 652 new security patches across its products, including 11 for Java SE. Oracle says all 11 Java SE flaws may be remotely exploitable without authentication, with the highest score among them 8.1 under CVSS 3.1.
Oracle lists the affected builds as Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, along with GraalVM for JDK 17.0.21 and 21.0.13, GraalVM Enterprise Edition 21.3.20.0.3, and JavaFX 21.0.13, 25.0.5 and 27.0.1. Oracle advised customers to stop using the existing builds after the update and move to the replacement releases listed in its JDK release notes.
Korean-language reports put the disclosure of the reported Java 17 flaw at 6am on Wednesday 18 November Korea Standard Time, which is 1pm Pacific time on Tuesday 17 November. Security firm watchTowr said it was aware of public reports of an unauthenticated remote code execution flaw in Java, while stressing that the details remain unconfirmed.
What administrators should do now
Organisations running Java should apply Oracle's November update as soon as the fixed builds are available, and patch every Java line they run, not only Java 17, because Oracle lists Java SE 8, 11, 17, 21, 25 and 27 as affected by the 11 flaws. Until a fixed build is published, there is no confirmed workaround or configuration change for the reported CVE-2026-114938 flaw.
The incident follows an emergency Java update from Oracle in October for CVE-2026-91403, a certificate trust flaw. Because the CVE record for CVE-2026-114938 is still reserved with no public description, it does not yet appear in CISA's Known Exploited Vulnerabilities catalogue. Administrators should watch the OpenJDK Vulnerability Group advisory page, where the upstream fixed versions and affected-release matrix are expected to appear.
Frequently asked questions
Is CVE-2026-114938 being exploited in the wild? As of 17 November, no vendor, government agency or researcher has reported exploitation in the wild, and no public proof-of-concept code has been published.
Which Java versions are affected? Early reports tie the reported flaw to OpenJDK 17.0.6 and later Java 17 updates. Oracle's November update separately lists Java SE 8, 11, 17, 21, 25 and 27 builds as affected by its 11 Java SE patches.
Source: Cyber Security News, with further detail from Aikido.