Oracle ships Java fixes while an OpenJDK flaw is reported
Oracle shipped Java SE fixes on November 17, 2026, and an OpenJDK remote code flaw is reported. See what to check on servers and in containers.
TL;DR: Oracle released fixes for Java SE on November 17, 2026, and a separate report warns of a critical OpenJDK flaw. If you run Java on servers or in containers, plan to update and confirm which build each one uses.
What happened
The Hacker News reported that Oracle would ship patches for several Java SE vulnerabilities on November 17, 2026, all of them exploitable remotely without a login. The report quotes Oracle's advance notice for a highest CVSS 3.1 score of 8.1, and says other reports warn of a possibly critical remote code execution flaw in OpenJDK. Read the original report from The Hacker News for the full story.
One of the Oracle entries is CVE-2026-114938, in the compiler component of Oracle Java SE and GraalVM. NVD records a CVSS v3.1 score of 8.1 from Oracle and describes a flaw that is difficult to exploit but can lead to takeover when data is supplied through APIs, for example in a web service. NVD lists the weakness as CWE-122, and the record does not name fixed versions, so use Oracle's own advisory for them.
Am I affected?
Any server, container image or build agent that runs Java SE or GraalVM may be in scope. Oracle's description lists affected builds on several release lines, so compare your exact build with Oracle's advisory rather than the major version alone. OpenJDK builds from your Linux distribution are separate products, so check your distribution's advisory too. To see what one machine runs:
java -versionRun it inside each container as well, because the Java in the image is the one that counts.
How to check with Stackurity
Stackurity finds Java found by its agent on Linux servers and in the images of running containers, and matches it against advisories and the CISA catalogue every hour, so one list shows every machine that needs the update. It checks again after the upgrade and records whether the issue is gone. It does not cover libraries copied into an application outside a package manager. See the verification guide for the recheck, or start a free trial.
Sources: The Hacker News and NIST National Vulnerability Database.