On this page (7 sections)

On 5 November 2026 Ubuntu published USN-9001-1, an update for the ca-certificates and ca-certificates-java packages. The notice says the JKS keystore integration was not working properly, so CA certificates removed from the system bundle were not being removed from the JKS keystore.

If you administer Ubuntu 22.04 LTS, 24.04 LTS, 26.04 LTS or 26.10 systems, this is worth applying as a routine update. The notice does not assign a CVE or a severity, and it does not say the problem is being exploited.

What the notice says

Ubuntu describes a functional bug rather than a classic code flaw. According to the notice, the ca-certificates JKS integration was not working properly, which meant CA certificates removed from the system bundle were not removed from the JKS keystore. JKS is a Java keystore format, and the ca-certificates-java package is described in the notice as providing the JKS keystore.

The update corrects the feature and, in Ubuntu's words, resyncs the keystore with the system CA certificates list. The notice links to Launchpad bug 2061817 as its reference.

Why a stale trust store can matter

The notice gives no impact details: it does not describe an attack, does not say which CAs were affected, and does not explain why any CA was removed from the bundle. The following is general background, not a claim from the notice.

A trust store is the list of certificate authorities that software will accept. If a keystore keeps entries that were taken out of the system bundle, it no longer matches the system list, which is the inconsistency this update is meant to correct. How much that matters for you depends on which CAs were removed and on whether your own software reads this keystore. Treat the practical impact as unconfirmed.

Fixed package versions

The notice lists these fixed versions per release. Ubuntu says updating to these package versions corrects the problem.

Fixed versions from USN-9001-1
Ubuntu releaseca-certificatesca-certificates-java
26.1020260816ubuntu0.26.10.220260311ubuntu0.26.10.1
26.04 LTS20260816ubuntu0.26.04.220260311ubuntu0.26.04.1
24.04 LTS20260816ubuntu0.24.04.220240118ubuntu0.24.04.1
22.04 LTS20260816ubuntu0.22.04.220190909ubuntu1.4

Who is affected

Based on the notice, the affected systems are those running one of these Ubuntu releases with the ca-certificates or ca-certificates-java packages installed:

  • Ubuntu 26.10
  • Ubuntu 26.04 LTS
  • Ubuntu 24.04 LTS
  • Ubuntu 22.04 LTS

The notice says nothing about other distributions, containers or Java installations. As general guidance (our inference, not from the notice), a container image built on one of these releases will only get the fix once you rebuild it on an updated base, so it is worth checking images you maintain.

How to check and update

The following read-only command lists the installed versions of both packages on Ubuntu. Compare the output with the table above.

Show installed ca-certificates versions (Ubuntu)Shell
dpkg -l ca-certificates ca-certificates-java

Ubuntu says a standard system update will make all the necessary changes. This refreshes package lists and upgrades only these two packages.

Update the two packages (Ubuntu, run as root or with sudo)Shell
sudo apt update
sudo apt install --only-upgrade ca-certificates ca-certificates-java

Afterwards, run the dpkg command again and confirm the versions match or exceed your release's row in the table.

ca-certificates-java may not be installed on hosts without Java. In that case dpkg reports it as not installed, and only the ca-certificates update applies.
Caution. The notice does not say whether a restart is required. As a general precaution, a long-running Java process may have read its keystore at startup, so if the keystore contents matter to your service, restart it in a maintenance window according to your own change process.

What to do now

  1. Run dpkg -l ca-certificates ca-certificates-java on each Ubuntu host and note the versions.
  2. Apply the standard update on 22.04, 24.04, 26.04 and 26.10 systems.
  3. Confirm the installed versions match the fixed versions in USN-9001-1.
  4. Restart Java services in a planned window if you need them to reload the keystore.
  5. Rebuild and redeploy container images that use an Ubuntu base, if you maintain any.

Monitoring afterwards

Keep an eye on the certificates your public sites present, since unexpected issuer changes are worth investigating. A free SSL certificate checker helps with a one-off look, and certificate and DNS monitoring can alert you to changes over time. Neither inspects the keystore on your servers, so patching remains the fix for this notice.

For other recent Ubuntu notices, see USN-9000-1 on Twisted and USN-8996-1 on APT. Only Ubuntu has published USN-9001-1 so far, so details beyond the notice are limited.

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. USN-9001-1: ca-certificates update | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • ca-certificates
  • Java
  • TLS
  • USN