On this page (7 sections)

Ubuntu published USN-9015-1 on 2026-11-09, covering multiple vulnerabilities in OpenJDK 21. The notice names problems in the Security, JSSE, Compiler, JAAS, JDBC and Networking components. Three of the CVEs it lists (CVE-2026-83374, CVE-2026-83376 and CVE-2026-83378) are also published by NVD with references to Oracle's October 2026 Critical Patch Update.

If you run OpenJDK 21 from Ubuntu packages for web applications, APIs, build servers or application servers, this notice is for you. The three CVEs with public scores are rated low to medium, but the notice covers many components, so it is worth reading in full and updating.

What the notice covers

Ubuntu's notice describes issues in OpenJDK 21 components. For the Security, JSSE, Compiler, JAAS, JDBC and Networking components it says the component did not correctly authenticate or authorize users. In the entries we could read, Ubuntu says a remote attacker could possibly read or modify sensitive data. For CVE-2026-83378 (Compiler) it specifies an unauthenticated remote attacker.

The notice text available to us ends partway through the Networking entry, so the full notice may list more CVEs than the six we can name. Read it before you sign off on a fleet.

Oracle's records for CVE-2026-83374, CVE-2026-83376 and CVE-2026-83378 describe the same CVE IDs against Oracle Java SE (and, for the first two, Oracle GraalVM for JDK and GraalVM Enterprise Edition). We have not confirmed how the other CVEs in the Ubuntu notice relate to Oracle's update.

Technical details of the scored CVEs

CVEs with published scores (source: NVD data via the GitHub Advisory Database)
CVEComponentCVSS 3.1Impact per advisoryWeakness
CVE-2026-83374Security5.9 (Moderate)High integrity impact: unauthorized creation, deletion or modification of critical dataCWE-200
CVE-2026-83376JSSE (TLS)3.7 (Low)Low integrity impact: unauthorized update, insert or delete of some dataCWE-200
CVE-2026-83378Compiler4.8 (Moderate)Low confidentiality and low integrity impactCWE-284

All three share the same vector: network access, high attack complexity, no privileges and no user interaction. High complexity means the attacker needs conditions outside their control, which is why the scores stay modest. The advisories note the flaws can be reached by supplying data to the affected APIs, for example through a web service that passes input into them.

CVE-2026-83374 and CVE-2026-83376 also apply to deployments that load and run untrusted code and rely on the Java sandbox, such as sandboxed Java Web Start applications or applets. CVE-2026-83378 is described as exploitable only by supplying data to the Compiler component's APIs, not through untrusted Web Start applications or applets.

Oracle's records list these affected Oracle Java SE versions: 8u503, 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1 and 27 for CVE-2026-83374 and CVE-2026-83376, and 21.0.12.1, 25.0.4.1 and 27 for CVE-2026-83378. These are Oracle's version numbers, not Ubuntu package versions, so use the Ubuntu notice to decide what to install.

The GitHub advisories are marked Unreviewed and list no package or fixed version. CVE-2026-83380, CVE-2026-83381 and CVE-2026-83387 are named in the Ubuntu notice, but the research gives no scores for them, so we do not rate them here.

Who is realistically exposed

The points below are general guidance based on how the advisories describe the flaws, not findings from the sources about specific products.

  • Servers running OpenJDK 21 from Ubuntu packages, such as web apps, APIs, CI runners and application servers.
  • Services that accept data from the internet and pass it to Java libraries, since the advisories say exploitation can happen through a web service that supplies data to the affected APIs.
  • Services using Java TLS (JSSE) or database connections (JDBC), since those components are named in the notice.
  • Hosts with a JDK that did not come from the Ubuntu package, for example one bundled in a container image or application bundle. As general practice, updating the Ubuntu package does not change a separately shipped JDK, so check those yourself.

How to check your exposure

First find out which Java runtimes are installed and which one your services use. This prints the version of the default Java on the PATH; run it on the host and compare against the notice.

Show the default Java version (any Linux host)Shell
java -version

On Ubuntu, this lists installed OpenJDK packages and their versions. Look for entries starting with openjdk-21 and note the version column.

List installed OpenJDK packages and versions (Debian/Ubuntu)Shell
dpkg -l | grep -i openjdk

This shows the installed and candidate versions of the headless runtime package, so you can see whether an update is already available. Compare the candidate with the fixed version in the Ubuntu notice for your release.

Show installed and candidate versions of the JRE headless package (Debian/Ubuntu)Shell
apt-cache policy openjdk-21-jre-headless
Tip. Check running processes too. A long-running service keeps using the old Java libraries in memory until it restarts, even after the package has been updated.

What to do now

  1. Open USN-9015-1 and note the fixed package versions for your Ubuntu release.
  2. Inventory every host and container that runs OpenJDK 21, including build agents and staging systems.
  3. Update the OpenJDK 21 packages through apt on each host (commands below).
  4. Restart Java services so they load the updated runtime, in a maintenance window if needed.
  5. Rebuild and redeploy container images and application bundles that ship their own JDK.
  6. Re-run java -version and the dpkg query to confirm the version matches the notice.

This refreshes package lists and upgrades only the named runtime package. Run it with sudo on Debian or Ubuntu.

Update the OpenJDK 21 headless runtime (Debian/Ubuntu)Shell
sudo apt update && sudo apt install --only-upgrade openjdk-21-jre-headless

If you also installed the full JDK or other OpenJDK 21 packages, a general upgrade will pick them up. Review what apt proposes before confirming.

Upgrade all pending packages (Debian/Ubuntu)Shell
sudo apt update && sudo apt upgrade
Caution. Restarting a Java service interrupts the requests it is handling. Restart production services one node at a time behind a load balancer, or in a planned window, and test the application afterward.

After updating, restart the service that uses Java. This example restarts a systemd unit; replace myapp with your own unit name.

Restart a systemd-managed Java service (replace myapp with your unit name)Shell
sudo systemctl restart myapp

Detection and monitoring afterward

No exploitation is reported in the sources we reviewed, so there is no specific indicator to hunt for. Focus on hygiene: keep a list of Java versions across your estate, subscribe to Ubuntu security notices, and re-check after each quarterly Oracle update. Watch application logs for unusual authentication or authorization errors in services that use JSSE, JDBC or JAAS, and review access to the data stores your Java services write to.

Because TLS handling is one affected area, confirm your public endpoints still present a valid certificate after restarts. The free SSL certificate checker can do this from outside, and monitoring can alert you if a certificate or header changes unexpectedly. For broader upkeep habits, see our small business website security guide.

Timeline

Summary
DateEvent
2026-10-20CVE-2026-83374, CVE-2026-83376 and CVE-2026-83378 published by NVD, with references to Oracle's October 2026 CPU
2026-10-21GitHub Advisory Database publishes the matching advisories
2026-10-27GitHub advisories last updated
2026-11-09Ubuntu publishes USN-9015-1 for OpenJDK 21

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.

  1. CVE-2026-83374 - GitHub Advisory Databasegithub.com
  2. CVE-2026-83376 - GitHub Advisory Databasegithub.com
  3. CVE-2026-83378 - GitHub Advisory Databasegithub.com
  4. USN-9015-1: OpenJDK 21 vulnerabilitiesubuntu.com ·
  • OpenJDK
  • Ubuntu
  • Java
  • USN
  • Patch management