On this page (7 sections)
On November 9, 2026, Ubuntu published USN-9004-1, a security notice for OpenJDK 25. It bundles fixes for several flaws that Oracle disclosed in its October 2026 Critical Patch Update, touching the 2D, Networking, JGSS and Security components of the Java runtime. On November 17, Ubuntu followed up with USN-9004-2, which corrects a regression introduced by the first update.
If you run Java applications on Ubuntu servers, such as web apps, APIs, build agents or application servers, these notices are relevant to you. The highest-scored flaw in the research is rated 7.0 (High), all three detailed records are rated difficult to exploit, and no active exploitation is reported. It is still a routine update worth scheduling soon, and the follow-up notice means you should install the latest package rather than stop at the first one.
What happened
Oracle's October 2026 Critical Patch Update covered Java SE and GraalVM. Ubuntu's notice maps the OpenJDK 25 side of that update to Ubuntu packages. The notice lists a long run of CVEs across components including 2D, Networking, JGSS, Security, JAXP, JDBC, JAAS, JSSE, ImageIO, Libraries, Lightweight HTTP Server and Compiler, and the excerpt available to us is cut off partway, so the full list may be longer. Read the complete notice before you plan your rollout.
On November 17, 2026, Ubuntu published USN-9004-2. It states that USN-9004-1 introduced a regression in OpenJDK 25 because the fix included an unnecessary debuginfo file, and that the new update fixes the problem. The notice does not describe any change to the security fixes themselves, and it lists the same Ubuntu releases (26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS). The research gives no further detail on how the extra file affected systems.
The research does not include the fixed package versions. Those details are in the notices themselves, and we do not guess them here.
Technical details
Three of the CVEs have full records in the National Vulnerability Database, mirrored by GitHub advisories. All three are rated as difficult to exploit (attack complexity High), need no privileges and no user interaction, and are reachable over the network.
| CVE | Component | CVSS 3.1 | Main impact | Weakness |
|---|---|---|---|---|
| CVE-2026-91415 | 2D | 7.0 High | Hang or repeatable crash (complete DoS), limited data read and modification | CWE-20 Improper Input Validation |
| CVE-2026-91398 | Networking (SOCKS5) | 6.8 Medium | Creation, deletion or modification of critical data, with a scope change | CWE-284 Improper Access Control |
| CVE-2026-91382 | 2D | 6.5 Medium | Data modification and partial denial of service | CWE-284 Improper Access Control |
In plain terms, CWE-20 means the code accepts input without checking it properly, and CWE-284 means access to something is not restricted as it should be. Oracle notes that these flaws can be reached by calling the affected APIs, for example through a web service that passes data to them. They also apply to clients that run sandboxed Java Web Start applications or applets with untrusted code. Most server deployments are in the first group: the risk depends on whether your application feeds outside data into the affected Java APIs.
The other CVEs in the notice (CVE-2026-91411 in JGSS and CVE-2026-83395 in Networking, among many more) are summarized by Ubuntu as allowing denial of service, or reading or modification of sensitive data, depending on the entry. The research gives no scores or further technical detail for them.
Who is affected
Oracle lists Java SE 8u503, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1 and 27 as affected for CVE-2026-91415 and CVE-2026-91398. CVE-2026-91382 lists 8u503, 11.0.32.1 and 17.0.20.1 only. Ubuntu's notices are about OpenJDK 25, so that is the package line they fix. If you run other OpenJDK versions on Ubuntu, such as 8, 11, 17, 21 or 27, check Ubuntu's security notices for the updates that cover those packages; this article does not confirm what they contain.
You are most exposed if a Java service takes data from the internet, for example file or image processing, or traffic through a SOCKS5 proxy. Internal-only services and desktop Java are lower priority, but should still be updated in the normal cycle.
Exploitation looks unlikely in the short term based on the research. The EPSS estimates for the three detailed CVEs are low (0.239%, 0.231% and 0.377%), and none appears in CISA's known exploited list. EPSS is a probability estimate, not a guarantee.
How to check your exposure
First, find out which Java runtime your service actually uses. This command prints the active version on the server (run it as the user that runs your app):
java -versionNext, list installed OpenJDK packages on Ubuntu. Look for any package with 25 in its name and compare its version with the version named in the Ubuntu notices, making sure it includes the USN-9004-2 update:
apt list --installed 2>/dev/null | grep -i openjdkAlso check containers and bundled runtimes. Container images that ship their own JDK, and applications with an embedded runtime, are not updated by the host's package manager.
What to do now
- Read the full USN-9004-1 and USN-9004-2 notices and note the package version for your Ubuntu release.
- Inventory every server, container image and build agent that uses OpenJDK 25.
- Refresh package lists and install the updated OpenJDK packages (commands below). If you already applied USN-9004-1, run the update again to pick up USN-9004-2.
- Restart Java services so they load the new runtime, then confirm the version again.
- Rebuild and redeploy container images that bundle OpenJDK 25.
- If you also run other OpenJDK versions (8, 11, 17, 21, 27), look up their notices in Ubuntu's security notices and apply them.
- Where possible, avoid exposing Java services that process untrusted input directly to the internet.
This refreshes the package index and upgrades installed packages from Ubuntu's repositories, including OpenJDK. Run it on each affected server; it should bring in both the security fixes and the regression fix:
sudo apt update
sudo apt upgradeAfter the restart, run the version check again and compare it with the version in the Ubuntu notices.
Detection and monitoring
The research reports no known exploitation and gives no indicators of compromise, so there is no specific signature to hunt for. General signals are still worth watching on Java services: unexplained crashes or hangs (the 2D issue can cause denial of service), unexpected restarts, and unusual outbound or SOCKS5 proxy connections from application hosts.
Keep a simple record of which Java version each service runs, so the next Oracle quarterly update is a quick lookup rather than a search. Plan for recurring patch windows, and expect that a follow-up notice such as USN-9004-2 can arrive after the first one. For a broader routine, see our small business website security guide. If you want uptime and certificate changes watched after a restart, Webforta Monitor can do that, though it does not detect these Java flaws.
Timeline
- 2026-10-20: Oracle's CVE records for CVE-2026-91415, CVE-2026-91398 and CVE-2026-91382 published in the NVD.
- 2026-10-21: GitHub advisories published for the three CVEs.
- 2026-11-09: Ubuntu publishes USN-9004-1 for OpenJDK 25.
- 2026-11-17: Ubuntu publishes USN-9004-2, fixing a regression in OpenJDK 25 caused by an unnecessary debuginfo file included in the USN-9004-1 update.
Story updates
Ubuntu published USN-9004-2 on November 17, 2026, fixing a regression that USN-9004-1 introduced in OpenJDK 25 (an unnecessary debuginfo file). The article now covers that follow-up and advises installing the latest package.
First published.
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.
