Hack

APT Flaw CVE-2026-109518: Update apt on Ubuntu Servers Now

An APT flaw lets an attacker on the network path install unsigned packages as root. Fixed versions, update commands and…

5 November 2026  ·  4 min read  ·  Anand

APT Flaw CVE-2026-109518: Update apt on Ubuntu Servers Now

A high-severity flaw in APT, the package manager on Debian, Ubuntu and their derivatives, can let an attacker get a package installed that fails signature verification. Packages install as root, so a successful attack gives the attacker full control of the server. The flaw is tracked as CVE-2026-109518, with a CVSS 4.0 score of 7.7. Canonical published fixes for every affected Ubuntu release on November 4, 2026, and Debian has also released updated apt packages. Almost every Debian-family server runs APT, often on a schedule, so this is an update to apply now. Pay particular attention to the way you install it.

How the attack works

Max Justicz found the flaw and disclosed it responsibly. According to Canonical’s advisory, exploitation needs all of the following:

  • Control of HTTP traffic. The attacker must be able to change traffic between your server and the package archive, for example on a shared or compromised network. A malicious mirror can also exploit it. HTTPS sources protect against the network attack, and FTP sources are not affected.
  • A download retry. APT must retry a failed download. If Acquire::Retries is set to 0, the flaw cannot be exploited.

When those conditions are met, APT can install a package that fails signature checking. This defeats the main protection that signed repositories provide. The flaw affects every APT-based frontend: apt, apt-get, aptitude and Ubuntu’s graphical software tools. Snap packages are not affected. The advisory does not report exploitation in the wild.

Ubuntu 22.04 LTS and later are vulnerable with default settings. Older releases are vulnerable only if retries have been turned on.

Fixed apt versions for Ubuntu

Release Fixed apt version
26.10 3.3.3ubuntu0.1
26.04 LTS 3.2.1ubuntu0.1
24.04 LTS 2.8.4ubuntu0.1
22.04 LTS 2.4.15ubuntu0.1
20.04 LTS (ESM) 2.0.12+esm1
18.04 LTS (ESM) 1.6.19+esm1
16.04 LTS (ESM Legacy) 1.2.36+esm1
14.04 LTS (ESM Legacy) 1.0.1ubuntu2.24+esm4

Fixes for 20.04 and earlier come through Ubuntu Pro (ESM). Releases 16.04 and 14.04 also need the Legacy add-on.

How to update safely

The vulnerable code is the same APT you use to install the fix, so disable retries for this one run. First, check which version you have:

apt list --installed '?source-package(^apt$)'

Then upgrade everything with retries turned off. This is Canonical’s recommended approach:

sudo apt update && sudo apt upgrade -o Acquire::Retries=0

If a full upgrade is not possible right now, for example during a change freeze, upgrade only APT:

sudo apt update && sudo apt install -o Acquire::Retries=0 --only-upgrade '?source-package(^apt$)'

Run the version check again afterwards and compare the result with the table. On Debian, install the apt update from the Debian security archive, and pass the same -o Acquire::Retries=0 option to the upgrade command.

On Ubuntu, unattended-upgrades is on by default and should install the fix within 24 hours. Do not assume it has worked, though. Check the installed version, especially on servers where automatic updates were turned off or pinned.

Harden your APT sources

Switch Ubuntu archives to HTTPS

Once the fix is installed, Canonical treats HTTPS as an extra precaution rather than a requirement. It is still worth doing on cloud hosts and any server whose network path you do not fully trust. This command rewrites the official Ubuntu archive URLs. It does not change third-party mirrors.

sudo sed -Ei 's!http://((([a-z]+\.)?archive|security|ports)\.ubuntu\.com)!https://\1!' /etc/apt/sources.list /etc/apt/sources.list.d/*.list /etc/apt/sources.list.d/*.sources
sudo apt update

Make sure apt update finishes without errors. Some community mirrors do not support HTTPS.

Fleet checklist

  • Find any hosts where retries are turned on: apt-config dump | grep -i retries.
  • Check that automatic updates are enabled: cat /etc/apt/apt.conf.d/20auto-upgrades.
  • Check that every server, container base image and CI runner has a fixed apt version. Rebuild Docker images that start from Debian or Ubuntu bases.
  • Review third-party and internal mirrors, and move them to HTTPS where you can.
  • Find out which old 18.04 or 20.04 machines lack Ubuntu Pro coverage, and either enrol them or upgrade them.

How TechProvidence can help

Patching one server takes a minute. Confirming that every server, image and build runner is patched takes longer. TechProvidence handles patch management, fleet audits and security hardening for Ubuntu and Debian servers, including mirror configuration, unattended-upgrade policies and upgrades away from end-of-life releases. If you want your APT estate checked and locked down, contact us.

Source: Ubuntu Blog

Running into something similar?

We look after Linux servers, control panels and virtualization for businesses every day. If an update, vulnerability or outage here affects you, we can help.