Find a practical answer

Search SmallGrid

Popular: Jellyfin, Docker, Ubuntu Server, Proxmox, backups and mini PCs.

← All home lab updates

Docker update

Docker Engine 29.9.3 Security Update: What Home Server Users Need to Know

Docker 29.9.3 fixes RSA and zstd denial-of-service risks, Swarm and BuildKit vulnerabilities, and a daemon hang. Check exposure and update Ubuntu hosts safely.

Published 09 Nov 2026High impactAction recommended

Quick answer

Docker Engine 29.9.3 was released on 3 November 2026. This security and maintenance patch addresses crafted RSA keys, zstd decompression, two Swarm-specific security issues and two BuildKit vulnerabilities. It also repairs a daemon-hanging bug under load.

Not every Docker host is exposed in the same way. A normal home server running a few Docker Compose applications is not automatically a Swarm cluster. BuildKit issues matter particularly when a host builds images or grants access to its BuildKit control API. However, the general Engine dependency fixes and daemon stability improvements still make a supported patch worth applying.

As of 9 November, 29.9.3 is the current stable release in Docker’s 29.x line. If you already run it, confirm the installed server version and verify the services rather than reinstalling anything. For a complete, backup-first procedure, use How to Safely Update Docker Engine on Ubuntu.

What changed in Docker Engine 29.9.3?

The official release notes identify these security fixes:

ComponentIssueWhen it matters
Engine dependenciesCVE-2026-116587: crafted RSA keys can cause excessive CPU useAffected key-parsing paths
Engine dependenciesCVE-2026-116591: crafted zstd-compressed data can cause a panicAffected decompression paths
Swarm overlay networkingCVE-2026-115538: encryption and anti-spoofing protections can be missing after firewalld flushes Docker-managed iptables rulesSwarm nodes with the described firewall interaction
SwarmKitCVE-2026-115539: someone already holding a valid worker-node TLS certificate and its private key could obtain a manager-node certificate shortly after a leader changeSwarm clusters and their certificate trust boundary
BuildKitGHSA-2fqp-xg6f-v7gj: resolving the same Git source reference metadata twice could poison a resolver cache and crash the daemonBuilds using the affected Git-source workflow
BuildKitGHSA-w26x-xg27-7qjc: a malicious client able to use BuildKit control APIs could set extended attributes outside BuildKit’s state directoryUntrusted access to BuildKit control APIs

The patch bundles BuildKit 0.34.2. The notes also document a fix for Docker daemon requests for containers, images and system information hanging under load.

These are vulnerabilities and defects confirmed by Docker, not evidence of an incident on your particular server. The practical response is to determine which components you use, patch through your existing supported package source and verify the workloads.

Ordinary Compose hosts versus Swarm and BuildKit

A typical Jellyfin/Sonarr/Radarr setup uses Docker Engine, Compose and local networks. It often does not run a Swarm manager, encrypted multi-node overlay networks or untrusted image builds.

  • Standalone Engine + Compose: update the Engine; test normal pulls, container starts, storage mounts, networking and the Docker API. The RSA/zstd and daemon fixes may still be relevant.
  • Swarm: prioritise the overlay-network and manager-certificate fixes. Review which hosts possess worker credentials, firewall behaviour and the cluster’s update plan.
  • BuildKit: review who can trigger builds and whether they can supply Git sources or access the BuildKit API. Do not expose builder control endpoints to untrusted users.
  • Docker Desktop or non-Ubuntu packages: follow your own vendor’s supported release path. Do not paste Ubuntu Apt commands onto those systems.

For SwarmKit’s certificate issue, the advisory requires an attacker to possess both a valid worker-node certificate and its private key. A random internet client without those credentials is not automatically in that position. Conversely, anyone who already controls worker credentials must not be treated as equivalent to an authorised manager.

Do not turn off Swarm overlay encryption or weaken firewall rules in response to the advisory. Apply the patch and validate the intended protections.

1. Identify the Engine and Compose versions

On the Docker host:

docker version
docker version --format 'client={{.Client.Version}} server={{.Server.Version}}'
docker compose version
docker buildx version

The server line is the Engine daemon you need to patch, not simply the client program on your laptop.

Check whether the host is in Swarm mode:

docker info --format 'Swarm state: {{.Swarm.LocalNodeState}}'

A result of inactive means the daemon is not currently participating in a Swarm. If it is active, do not change firewall or node membership without checking the cluster’s documented maintenance process.

To inspect container versions and status before maintenance:

docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'
docker compose ls
docker network ls
docker volume ls

The presence of docker buildx does not prove that untrusted build workloads have been run. It is one clue about the installed tooling, not a vulnerability scan.

2. Check Ubuntu’s package source and update candidate

First confirm how Docker was installed:

cat /etc/os-release
apt-cache policy docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
dpkg-query -W 'docker*' 'containerd*' 2>/dev/null

If Docker came from Ubuntu’s docker.io packages, a snap, a vendor appliance or another repository, do not mix it with Docker Inc.’s docker-ce packages during a routine security patch. Use the correct vendor update path and check whether the patch has been backported.

For hosts using Docker’s official Ubuntu Apt packages, refresh and preview:

sudo apt update
apt list --upgradable 2>/dev/null | grep -Ei 'docker|containerd'
sudo apt-get -s upgrade

Review the candidate versions and proposed removals before agreeing to the transaction. The availability of 29.9.3 depends on your Ubuntu release and configured repository.

3. Back up before updating the daemon

An Engine patch is not an application-image upgrade. Keep the maintenance window focused.

For each important stack, preserve:

  • the original Compose files, .env files and secrets
  • bind-mounted application configuration, databases and media metadata
  • the names and locations of persistent volumes
  • a recoverable database backup where the application requires one
  • the currently running image references and expected port mappings

Follow How to Back Up and Restore Docker Compose Services and, for the precise host-side sequence, How to Safely Update Docker Engine on Ubuntu.

Do not run docker compose down -v, delete /var/lib/docker or run docker system prune -a as a routine security update. Do not combine the Engine patch with a mass pull of application images.

If this server participates in a Swarm, plan a controlled cluster update with the documented leader/manager quorum requirements and verify encrypted overlay behaviour afterwards. Do not restart all managers together.

4. Apply the supported update

After backing up and reviewing the Apt simulation, update through your established package source. On a standard Ubuntu host with a supported Docker repository, an ordinary package update is:

sudo apt upgrade

This may upgrade other pending packages, not just Docker. If you need a Docker-only window, follow the package-specific instructions in SmallGrid’s safe Engine update guide and simulate the exact transaction first.

An update can restart the Docker daemon and interrupt application availability. Arrange a suitable window and console/SSH recovery access, especially on a server managed remotely.

5. Verify Docker and the services

After the package update:

docker version --format 'client={{.Client.Version}} server={{.Server.Version}}'
docker compose version
docker buildx version
systemctl status docker --no-pager
docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'
docker compose ls

Confirm the server reports the intended patched Engine build. Then verify the things that matter to your actual services:

  1. Check Jellyfin can see its media mounts and play a known file.
  2. Confirm Sonarr/Radarr can still see their configured download and library paths.
  3. Check proxy or VPN routes without changing container images.
  4. Inspect recent Docker journal entries if services restart or network access changes.
  5. For Swarm, verify manager quorum, service health, firewall state and overlay-network behaviour from trusted nodes.
  6. For BuildKit users, run a trusted, controlled build and confirm untrusted clients cannot reach build APIs.
sudo journalctl -u docker --since "30 minutes ago" --no-pager
docker network ls
docker volume ls

If a container remains stopped, investigate its logs and restart policy before changing volumes, images or network configuration. See Docker Container Keeps Restarting.

Does 29.9.3 fix the daemon hang?

Docker explicitly lists a fix for container, image and system API requests hanging under load. If you previously saw unresponsive docker ps, image requests or dashboard operations during heavy activity, this is a relevant regression fix.

It does not mean every slow Docker command was caused by this defect. Check storage I/O, containerd status, network and daemon logs before attributing a different symptom to a specific release.

Official sources


Recap

Docker Engine 29.9.3 is a security patch, not a reason to rebuild your home server. Work out whether you use standalone Compose, Swarm or BuildKit; preserve a recoverable state; patch the Engine from its supported source; and verify real applications afterwards. Swarm and BuildKit advisories deserve extra attention on hosts where those features are actually used.

Keep the permanent fix nearby

Affected SmallGrid guides

Primary source

This update is based on the official announcement: Docker Engine 29 release notes.