Skip to main content
Published on November 15, 2026
CVE-2026-109518 — APT, the Debian and Ubuntu package manager. An attacker on the network path, or a malicious mirror, can make APT install a package that failed signature verification. The package installs as root. Debian 12, Debian 13, and Ubuntu 22.04 and later are exposed in their default configuration. Update APT today, with download retries turned off while the fix installs.

The bug in two sentences

When an HTTP redirect gives two different downloads the same URI, APT can merge them. A file-handling error when resuming an HTTP download then lets an attacker replace a package after it has been verified: the APT team describes already-verified hard links being overwritten with a payload of the attacker’s choice. A .deb package runs its scripts as root during installation. The flaw therefore leads to root code execution on the machine. Requirements:
  • the attacker can tamper with HTTP traffic between the machine and the archive server: a proxy, an intermediate network, or a malicious mirror;
  • the machine installs a package during the attack;
  • APT is set to retry failed downloads (Acquire::Retries other than 0). That has been the default since APT 2.3.2, which means Debian 12 (bookworm) and Ubuntu 22.04 LTS.
Ubuntu, which assigned the CVE, scores it 7.7 under CVSS 4.0 and gives it high priority. NVD carries the same score. The APT team calls it critical. Max Justicz found the flaw; Debian and Ubuntu shipped fixes on November 4, 2026.
The flaw is not in CISA’s Known Exploited Vulnerabilities (KEV) catalog (November 13, 2026 version). It affects every tool built on APT: apt, apt-get, aptitude, and Ubuntu’s graphical software centers. Snap packages are not affected.

Sizing your exposure

The question to ask: does your machine fetch packages over HTTP, with retries turned on? That is the default on Debian 12, Debian 13, and Ubuntu 22.04 and later. To find out whether your sources use HTTP:
On an older release, to find out whether a script turned retries on:

Updating APT per distribution

The fix is an update of the apt package. Ubuntu recommends turning retries off while the fix installs: without retries, the flaw cannot be exploited, by an on-path attacker or by a malicious mirror. The update itself cannot be hijacked.

Debian

Ubuntu

The fixes ship in notice USN-8996-1. These are the commands Ubuntu recommends:
If you do not trust the network path to the archive, Ubuntu also suggests switching its sources to HTTPS before updating. The command only rewrites URLs of Ubuntu’s archive, security, and ports servers:
Some community and country mirrors do not serve HTTPS: apt update reports it as an error.

Docker containers

In a Debian or Ubuntu image, update APT before installing anything else, then rebuild the image:

Mitigation until you can patch

If you cannot update right away, turn retries off in APT’s configuration. This is the mitigation posted on oss-security alongside the Debian advisory: with no retry, the flaw’s precondition is gone.
With this setting, APT no longer retries a failed download: run the command again by hand if a download is interrupted.

Checking the mitigation

Reverting the mitigation

Once the fixed apt package is installed, remove the file to restore the default retries:

What next?

Archive signatures remain APT’s main safeguard, and the fix restores them. To have future fixes install without waiting, turn on automatic security updates on your VPS. For another recent flaw, read the Linux kernel TCP flaw (CVE-2026-98432). For any technical question, open a ticket from your OnetSolutions customer area.