On this page (7 sections)
Ubuntu published security notice USN-9009-1 on 2026-11-09. It covers multiple vulnerabilities in OpenJDK 8, the open source Java runtime many web applications, build servers and middleware depend on. A matching notice, USN-9010-1, covers OpenJDK 11 with the same list of CVEs.
If you run Java applications on Ubuntu, especially services that accept data from the network or make TLS connections, you should plan an update. None of the issues described in the research is a headline-grabbing remote code execution flaw, but several concern authentication, authorization and TLS handling, which are worth closing promptly.
What the Ubuntu notice says
The notice groups the OpenJDK 8 fixes by Java component. The excerpt available to us lists these items, each described as something a remote attacker could possibly abuse:
- Security component: did not correctly authenticate users, possibly allowing modification of sensitive data (CVE-2026-83374).
- JSSE component: did not correctly authorize users, possibly allowing modification of sensitive data (CVE-2026-83376, CVE-2026-91461).
- JAAS component: possible reading of sensitive data (CVE-2026-83380).
- Security component, authorization: possible reading or modification of sensitive data (CVE-2026-83381, CVE-2026-87294).
- JDBC component: possible reading of sensitive data (CVE-2026-83387).
- Networking component: possible denial of service or modification of sensitive data (CVE-2026-83395).
These identifiers also appear in Oracle's October 2026 Critical Patch Update, which is where the upstream Java fixes originate. Ubuntu repackages the OpenJDK fixes for its supported releases.
Technical details of the three CVEs with full records
The research includes NVD-derived records, mirrored in GitHub advisories, for three of the CVEs. All three are described as difficult to exploit, need no authentication or user interaction, and are reachable over the network. All three affect Oracle Java SE, Oracle GraalVM for JDK and GraalVM Enterprise Edition, and the advisories list the Oracle versions as 8u503, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1 and 27 among others.
| CVE | Component | CVSS 3.1 | Impact | Weakness |
|---|---|---|---|---|
| CVE-2026-83374 | Security | 5.9 (Medium) | Unauthorized creation, deletion or modification of critical data | CWE-200 |
| CVE-2026-83376 | JSSE (via TLS) | 3.7 (Low) | Unauthorized update, insert or delete of some data | CWE-200 |
| CVE-2026-91461 | JSSE (via TLS) | 3.7 (Low) | Unauthorized update, insert or delete of some data | CWE-295 |
In plain terms, CWE-200 is exposure of information to someone who should not have it, and CWE-295 is improper certificate validation, meaning software that does not properly check whether a certificate can be trusted. The 5.9 score is driven by high integrity impact: data could be altered, not read or taken offline. The high attack complexity in the vectors means an attacker needs conditions beyond their control, which is why the scores stay moderate or low.
Oracle's notes say the flaws can be reached by feeding data to the affected APIs, for example through a web service that passes data into them. For CVE-2026-83374 and CVE-2026-83376 they also apply to clients running sandboxed Java Web Start applications or applets that load untrusted code. CVE-2026-91461 is described as exploitable only through API data, not through untrusted Web Start applications or applets. GitHub marks these advisories as unreviewed, and they list no package or patched version, so the Ubuntu notice is the useful source for fixed builds.
The GitHub advisories show EPSS estimates of 0.289%, 0.252% and 0.187% for the three CVEs. These are probabilities of exploitation within 30 days, not confirmation of anything, and the research reports no active exploitation.
Who is realistically exposed
- Servers running Java web applications, APIs or message consumers on Ubuntu with OpenJDK 8 or 11 installed from Ubuntu packages.
- Applications that make or accept TLS connections through Java's built-in JSSE stack, which relates to CVE-2026-83376 and CVE-2026-91461.
- Services that use JDBC database connections, JAAS login modules or Java's networking classes, which relate to other CVEs in the notice.
- Build servers, CI runners and legacy internal tools, which often keep an old Java 8 runtime running unattended.
Desktop use of Java applets or Web Start is rare today, so the sandbox scenario is mostly relevant to old enterprise clients. For most website operators, the server-side API scenario matters more.
How to check your exposure
First find out which Java packages are installed and whether any process is actually running Java. This read-only command lists installed OpenJDK packages and their versions on Debian and Ubuntu; compare the versions to those listed in the full notice.
dpkg -l | grep -i openjdkThis command shows the active Java runtime version for the current user, which can differ from the packages you expect if several runtimes are installed.
java -versionThis lists running Java processes so you know which services will need a restart after patching.
ps aux | grep -i [j]avaWhat to do now
- Inventory every Ubuntu host and container that runs OpenJDK 8 or 11.
- Read the full USN-9009-1 and USN-9010-1 notices to confirm the fixed package versions for your Ubuntu release.
- Refresh the package index and upgrade the OpenJDK packages (commands below).
- Restart Java services so they load the patched runtime.
- Rebuild and redeploy container images that bundle OpenJDK from a base image.
- Re-run the version checks to confirm the new package is installed and no old runtime is still serving traffic.
This updates the package lists and then upgrades installed OpenJDK packages only. Replace the package name with the ones shown by the earlier dpkg command if yours differ.
sudo apt update
sudo apt install --only-upgrade $(dpkg -l | awk '/openjdk/ {print $2}')After the upgrade, restart each affected service, for example with systemd. Substitute your own unit name.
sudo systemctl restart your-service-nameDetection and monitoring afterwards
Because several of these flaws concern TLS validation and authorization, watch for odd behavior rather than a clear exploit signature: unexpected failed or successful TLS handshakes in application logs, unexplained changes to data written by services that accept external input, and Java processes restarting unexpectedly. Keep an eye on the Ubuntu security notices page for follow-up releases, since a second notice often adds fixes for other releases or corrections.
For public-facing sites, a free SSL certificate checker helps confirm your endpoints still present valid certificates, and monitoring for certificate and DNS changes can flag unexpected changes. These do not detect this Java flaw itself; patching is the fix. For related Ubuntu patching context, see our note on USN-9001-2 and the ca-certificates JKS keystore, which also touches Java trust stores.
Bottom line
USN-9009-1 is a routine but broad Java security update. Severity scores in the available records range from 3.7 to 5.9, and no exploitation is reported, so this is a scheduled-patching job, not an emergency. Still, Java runtimes tend to be forgotten on servers, so use this notice as a prompt to find them, update them and restart the services that use them. For broader habits, see our guide to small business website security.
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.
