On this page (7 sections)
Ubuntu published security notice USN-9005-1 on 2026-11-09 for OpenJDK 27. It lists several flaws across the 2D, Networking, Security, JAXP and JDBC components. The same Java SE issues were covered earlier in Oracle's October 2026 Critical Patch Update.
If you run Java applications on Ubuntu servers, build agents or containers based on OpenJDK 27, this is a routine but worthwhile update. None of the issues in the research is reported as exploited.
What the notice covers
Ubuntu's notice describes problems in several OpenJDK 27 components. For the 2D component (CVE-2026-91415) and the Networking component (CVE-2026-91398 and CVE-2026-83395), it says a remote attacker could possibly cause a denial of service or read or modify sensitive data. For the Security component (CVE-2026-83381, CVE-2026-87294) it describes possible reading or modification of sensitive data, and for JAXP (CVE-2026-87290) possible reading of sensitive data. The notice also mentions JDBC; the text we have is truncated there, so check the full page for the complete list.
Ubuntu words several of these as failures to correctly authenticate or authorize users. Oracle and NVD describe the same CVEs more narrowly, so treat the component and impact as the reliable part and the exact mechanism as not fully public.
The three best-documented CVEs
| CVE | Component | Score | Complexity | Main impact | Weakness |
|---|---|---|---|---|---|
| CVE-2026-91415 | 2D | 7.0 High | High | Complete DoS (hang or repeatable crash), some data change, partial data read | CWE-20 Improper Input Validation |
| CVE-2026-91398 | Networking (SOCKS5) | 6.8 Medium | High | Integrity of critical data, scope change | CWE-284 Improper Access Control |
| CVE-2026-83395 | Networking | 6.5 Medium | Low | Some data change, partial DoS | CWE-284 Improper Access Control |
All three need no privileges and no user interaction, and are reachable over the network according to the CVE-2026-91415, CVE-2026-91398 and CVE-2026-83395 advisories. CVE-2026-83395 is described as easily exploitable, while the other two are rated difficult to exploit. CVE-2026-91398 is limited to SOCKS5 access and carries a scope change, meaning an attack could affect more than Java itself.
The EPSS estimates in those advisories are low: 0.239%, 0.231% and 0.327% respectively, for exploitation within 30 days. That is a probability estimate, not a statement that attacks are absent.
Who is realistically exposed
- Servers running Java web services that pass outside data to Java APIs. Oracle notes these flaws can be reached through APIs, for example through a web service that supplies data to them.
- Java applications that use image handling (2D), network clients, SOCKS5 proxies (CVE-2026-91398) or XML parsing.
- Clients that run sandboxed Java Web Start applications or applets with untrusted code. Oracle says the issues also apply there, though this is rare today.
- Desktop-only or offline use is lower risk, since the attack path is network based.
Remember that the advisories do not list a vulnerable code path for your specific application. Exposure depends on whether your Java process handles untrusted input in the affected components.
How to check your exposure
First, see which Java runtime is installed and running. This read-only command lists installed OpenJDK packages on Debian and Ubuntu; look for openjdk entries and their version numbers.
dpkg -l | grep -i openjdkNext, print the version the system will actually use. A server can have several JDKs installed, and your service may use a bundled one.
java -versionThen check which running processes use Java, so you know what to restart after updating. This lists Java processes with their command lines.
ps aux | grep '[j]ava'What to do now
- Open USN-9005-1 and find the fixed package versions for your Ubuntu release.
- Inventory every host and container image that ships OpenJDK 27, including build servers.
- Update only the OpenJDK packages shown by the dpkg check, using the targeted command below.
- Restart Java services so they load the patched runtime.
- Rebuild and redeploy container images that bundle their own JDK.
- Confirm the new version with java -version and re-check the process list.
- If you cannot patch yet, restrict network access to Java services and any SOCKS5 proxy use to trusted sources.
This refreshes the package lists, then upgrades one installed package to its newest available version without touching other packages. Replace the placeholder with an exact package name from the dpkg output above, and repeat for each OpenJDK package you have installed. Afterwards, dpkg -l should show the newer version.
sudo apt update
sudo apt install --only-upgrade <package name from the dpkg check>Detection and monitoring after patching
There is no published indicator of compromise for these flaws, so focus on hygiene. Watch Java service logs for unexpected crashes or restarts, since CVE-2026-91415 can cause a hang or repeatable crash. Review unusual outbound or inbound SOCKS5 traffic and unexpected changes to application data.
Keep an eye on uptime and certificate state of Java-backed sites too; uptime monitoring helps you notice repeated crashes quickly, and Webforta Monitor can alert on availability and certificate changes. Check the Ubuntu notice again over the coming days, since the text we reviewed was incomplete and fixed versions may be easier to confirm there.
What is still unclear
- Fixed package versions per Ubuntu release are not in the research we reviewed.
- The Ubuntu notice text is truncated, so the full CVE list and the JDBC entry are not confirmed here.
- Ubuntu's wording about authentication and authorization differs from Oracle's component-level descriptions, and no public exploit details exist in the sources.
- No source reports active exploitation.
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.
