On this page (7 sections)
Ubuntu has published USN-9154-1, a security notice dated 2026-11-18 covering five vulnerabilities in OpenJDK 11. They sit in the JGSS, JSSE, Hotspot, Core Java Libraries and Compiler components, and they match the Oracle and OpenJDK vulnerability advisories released on 2026-11-17.
If you run Java 11 on Ubuntu servers, build agents or application hosts, this notice is for you. The Ubuntu excerpt we reviewed does not list fixed package versions or say whether any of these flaws are being exploited, so this article sticks to what is confirmed and tells you how to check your own systems.
What happened
On 2026-11-17 the OpenJDK project and Oracle released their quarterly vulnerability advisories (see the OpenJDK advisory referenced by Ubuntu and the Oracle alert). A day later Ubuntu shipped USN-9154-1 to carry the OpenJDK 11 fixes to its users.
Ubuntu describes all five issues as remote. In its wording, an attacker could possibly read or modify sensitive data, or in one case cause a denial of service.
The five issues in plain terms
| CVE | Component | What Ubuntu says | CVSS 3.1 (NVD record) |
|---|---|---|---|
| CVE-2026-114939 | JGSS | Did not correctly authenticate users; possible read or modification of sensitive data | 7.4 high |
| CVE-2026-114940 | JSSE | Did not correctly authorize users; possible read or modification of sensitive data. Credited to Nicholas Carlini | 7.4 high |
| CVE-2026-114943 | Hotspot | Did not correctly authorize users; possible denial of service or modification of data | 6.5 medium |
| CVE-2026-114944 | Core Java Libraries | Did not correctly authorize users; possible modification of sensitive data. Credited to Alexander Dezhinov, Stanislav Dukhin, Nikita Kozlov and Binbin Xu | Not in research |
| CVE-2026-114946 | Compiler | Did not correctly authorize users; possible read or modification of sensitive data | Not in research |
In short, these are authentication and authorization weaknesses inside core Java libraries. That class of bug means code that should be restricted by a check can be reached or abused without the right permission. The CVSS vector for the first three is network-reachable with no privileges and no user interaction, but with high attack complexity, which Oracle describes as difficult to exploit.
Who is realistically exposed
The Oracle records draw an important line, and it differs by CVE.
- CVE-2026-114939 (JGSS): per the record, it applies to Java deployments that load and run untrusted code and rely on the Java sandbox, typically clients running sandboxed Java Web Start applications or applets. It does not apply to deployments that run only trusted code, such as typical servers.
- CVE-2026-114940 (JSSE) and CVE-2026-114943 (Hotspot): the records say they can be exploited by using APIs in the component, for example through a web service that supplies data to those APIs. They also apply to the sandboxed untrusted-code case. A server application that passes outside data into TLS or affected APIs is therefore worth treating as potentially exposed.
- CVE-2026-114944 and CVE-2026-114946: the research gives no applicability notes, so assume any OpenJDK 11 install on Ubuntu is in scope until you have read the notice.
How to check your exposure
First find out whether Java 11 is installed and which package version you have. This command lists installed OpenJDK packages on Debian and Ubuntu and shows their versions; look for openjdk-11 entries.
dpkg -l | grep -i openjdkNext, confirm which Java a service actually runs. This prints the active runtime version; a 11.0.x result means your default is Java 11.
java -versionMany applications bundle their own JRE or use a path set in a service file, so the default may not be the one in use. Check the startup script or unit file of each Java service as well.
What to do now
- Inventory every host and container image that runs Java 11, including CI runners and build images.
- Read USN-9154-1 and note the fixed package versions for your Ubuntu release.
- Refresh package lists and install the updated OpenJDK 11 packages (commands below).
- Restart Java services so they load the patched runtime; a running JVM keeps the old code until restarted.
- Confirm the new version with dpkg and java -version after the restart.
- Rebuild and redeploy container images that bundle OpenJDK 11, since host updates do not change them.
- Replace or separately update any Oracle JDK or GraalVM installs, which Ubuntu updates do not touch.
- If you run applets or Java Web Start clients that execute untrusted code, prioritize those systems.
This updates only the OpenJDK packages on a Debian or Ubuntu system. The package name below follows the usual Ubuntu naming; adjust it to match what dpkg showed on your host.
sudo apt update
sudo apt install --only-upgrade openjdk-11-jre-headlessAfter the update, restart each service. Replace the name with your own unit.
sudo systemctl restart your-service-nameDetection and monitoring
The sources do not describe indicators of compromise or any exploitation, so there is no known signature to hunt for. Practical steps are to watch for unexpected authorization failures or crashes in Java application logs, since the Hotspot issue can cause a hang or repeatable crash, and to keep an eye on unusual TLS-related errors in services that terminate TLS in Java.
For public sites fronted by Java applications, Webforta Monitor can alert you to uptime and certificate changes, which helps you notice unplanned restarts or outages after patching. For wider patching habits, see small business website security.
Caveats and open questions
- The Ubuntu excerpt we reviewed does not list fixed versions, so confirm them in the notice itself.
- CVSS scores for CVE-2026-114944 and CVE-2026-114946 were not available in the research.
- The GitHub advisories for the first three CVEs are marked unreviewed and list no package or patched version, so they are not a basis for version checks.
- No source reported exploitation. Treat that as unknown rather than as proof of safety.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
