On this page (7 sections)

On October 28, 2026, the Debian security team published DSA-6591-1, an update for the openjdk-25 package that addresses a long list of vulnerabilities in the OpenJDK Java runtime. The advisory lists 40 CVE identifiers and says the problems may result in denial of service, sandbox breakout, incomplete certificate checks or information disclosure (Debian DSA-6591-1).

If you run Java applications on Debian 13 (trixie) using the openjdk-25 packages, such as application servers, build agents or internal services, you should plan this update. So far only the Debian advisory itself covers this story, so some details below are limited to what it states.

What Debian announced

DSA-6591-1 is a routine but large rollup. Debian packages the OpenJDK fixes as a single security update. The advisory states that for the stable distribution (trixie), the problems are fixed in version 25.0.5+8-1~deb13u1 and recommends upgrading the openjdk-25 packages (Debian DSA-6591-1).

The advisory does not give per-CVE descriptions, CVSS scores or any statement about active exploitation. For per-issue detail, Debian points to its security tracker page for openjdk-25. Until you have read the individual entries there, treat the severity of the batch as unknown rather than assuming it is low or high.

What the weakness classes mean

Debian groups the impact into four categories. In plain terms:

  • Denial of service: a crafted input or request can make a Java process hang, crash or use excessive resources. This matters most for services that accept data from untrusted users.
  • Sandbox breakout: Java can restrict what loaded code is allowed to do. A breakout means code could exceed those limits. This is most relevant if you run untrusted or semi-trusted code inside a JVM.
  • Incomplete certificate checks: TLS or signature validation may accept something it should reject. This weakens the guarantees of encrypted connections that your Java services make to other systems.
  • Information disclosure: data that should stay private could be exposed to a party that should not see it.

Which of these can be reached on your server depends on what your applications do with Java, and the advisory does not map individual CVEs to attack conditions.

Who is realistically exposed

The advisory names the stable distribution, trixie, and the openjdk-25 source package. You are in scope if a Debian 13 host has OpenJDK 25 installed from the Debian repositories. Common examples include servers running Tomcat or Jetty style applications, CI runners, search or messaging platforms written in Java, and containers built on a Debian 13 base image that install openjdk-25.

The research does not cover other Debian releases, other OpenJDK versions or other distributions, so do not assume this advisory applies to them. Java installed outside the package manager, such as a vendor tarball, is not updated by this advisory at all and needs to be checked separately.

How to check your exposure

The first command lists installed OpenJDK 25 packages and their versions on Debian. Any version older than 25.0.5+8-1~deb13u1 still needs the update.

List installed openjdk-25 packages and versions (Debian 13)Shell
dpkg -l 'openjdk-25*'

This command shows the version the package manager would install from your configured repositories, so you can confirm the fixed build is available to the host.

Show installed and candidate versions (Debian 13)Shell
apt-cache policy openjdk-25-jre-headless
The package name openjdk-25-jre-headless is a common Debian naming pattern, but the advisory only names the source package openjdk-25. If the command returns nothing, use the dpkg listing above to see which binary packages you actually have.

Also check which Java a service actually runs. A host can have several runtimes installed, and an application may be pinned to a different one or bundle its own. This prints the version of the default java command.

Show which Java the system default points toShell
java -version

What to do now

  1. Inventory Debian 13 hosts, VMs and container images that install openjdk-25.
  2. Run the dpkg check above and note any version older than 25.0.5+8-1~deb13u1.
  3. Read the Debian security tracker entries for the CVEs most relevant to how you use Java.
  4. Schedule the update, starting with internet-facing and multi-user systems.
  5. Apply the update with your package manager (commands below).
  6. Restart the Java services so they load the patched runtime.
  7. Rebuild and redeploy container images that bundle the old package.
  8. Find any Java installed outside the package manager and update it from its own vendor.

This updates the package index and upgrades only the OpenJDK 25 packages already installed on the host.

Update openjdk-25 packages (Debian 13, run as root or with sudo)Shell
sudo apt update
sudo apt install --only-upgrade 'openjdk-25*'
Caution. A running Java process keeps using the old runtime in memory until it is restarted. Restarting application services causes a brief outage, so schedule it for a maintenance window and restart nodes one at a time behind a load balancer where you can.

After restarting, this command confirms the installed version matches the fixed build; you should see 25.0.5+8-1~deb13u1 in the output.

Confirm the fixed version is installed (Debian 13)Shell
dpkg -l 'openjdk-25*' | grep 25.0.5+8-1~deb13u1

Detection and ongoing monitoring

The advisory gives no indicators of compromise, so there is nothing specific to hunt for. Reasonable general steps are to watch Java service logs for unexpected crashes, out-of-memory errors or restarts, which can be a symptom of denial of service, and to review outbound TLS errors after the update in case stricter certificate handling exposes misconfigured peers.

Subscribe to the debian-security-announce list or check the Debian tracker regularly so the next OpenJDK batch does not wait for a manual search. If your Java services sit behind a public website, keep an eye on certificates and response headers as well; a tool such as Webforta Monitor can alert you to certificate and header changes, and the free SSL checker gives a quick one-off look at a public endpoint. These do not detect these OpenJDK flaws, so they complement patching rather than replace it.

For a broader routine to keep servers and sites patched, see our guide to small business website security.

Timeline

Summary
DateEvent
October 28, 2026Debian publishes DSA-6591-1 with fixed version 25.0.5+8-1~deb13u1 for trixie

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. [SECURITY] [DSA 6591-1] openjdk-25 security updatelists.debian.org ·
  • Debian
  • OpenJDK
  • Java
  • DSA
  • Patch management