Skip to content
Techzovia
Tech News

Debian and Ubuntu patch an APT flaw that could let attackers run code as root

Debian and Ubuntu have fixed CVE-2026-109518, an APT bug that could let a malicious mirror or proxy install an unverified package as root. Here's how to update.

By Golam Moktadir3 min read
On this page

On November 4, 2026, Debian and Ubuntu released security updates for APT, the tool that installs and updates software on both distributions and their derivatives. The main bug, CVE-2026-109518, could let an attacker who can tamper with your package downloads get an unverified package installed with root privileges. If you run Debian or Ubuntu servers, desktops or containers, update APT now.

What happened

APT developer Julian Andres Klode announced the fixes on the Debian APT mailing list. Researcher Max Justicz reported the main bug. Ubuntu's description says an attacker who can manipulate the HTTP traffic between an APT client and an archive server, for example through a malicious mirror or proxy, could trick the client into installing an attacker-controlled package that was never verified. Because packages are installed as root, this could lead to remote code execution.

According to Klode, the attack abuses redirects and temporary HTTP server errors that make APT retry a download. The retry can cause APT to overwrite existing hard links with the attacker's file. Ubuntu rates the issue High priority, with a CVSS v4.0 score of 7.7.

The same update fixes several out-of-bounds memory bugs in APT. It also fixes an issue in the 2.6, 2.8 and 3.0 series where repeated error logging during retries could use up memory or fill the logs. Klode says the memory bugs mostly matter for programs that parse untrusted .deb files from a root process.

Patched versions published so far:

  • Debian 13 (trixie): apt 3.0.4, in advisory DSA-6607-1
  • Debian 12 (bookworm): apt 2.6.2, in LTS advisory DLA-4880-1
  • Debian unstable (sid): apt 3.3.6. When we checked, Debian's tracker still listed testing (forky) as vulnerable.
  • Ubuntu 26.10: 3.3.3ubuntu0.1
  • Ubuntu 26.04 LTS: 3.2.1ubuntu0.1
  • Ubuntu 24.04 LTS: 2.8.4ubuntu0.1
  • Ubuntu 22.04 LTS: 2.4.15ubuntu0.1
  • Ubuntu 20.04 LTS and older: fixed through Ubuntu Pro. The 16.04 and 14.04 fixes need the Legacy Support add-on.

Ubuntu's notice for these fixes is USN-8996-1.

Why it matters

APT checks every package against signed repository metadata before installing it. That check is the main reason it's considered safe to download packages over plain HTTP. This bug gets around it, so a compromised mirror, a hostile network or a tampered proxy could get code running as root on your machine.

There is one condition. Ubuntu says only clients with a non-zero Acquire::Retries setting are affected. Klode notes that retries have been on by default since APT 2.3.2. Ubuntu says the default of 3 applies from Debian 12 and Ubuntu 22.04 LTS onward, so most current systems are affected in their default setup.

None of the advisories or news reports we reviewed say the flaw has been exploited in the wild. They also don't offer a workaround besides installing the fixed packages.

What you should do

  1. Check your installed APT version. Run:

    apt-cache policy apt

    Compare the Installed: line with the fixed version for your release in the list above.

  2. Update. Refresh the package lists and install the update:

    sudo apt update
    sudo apt upgrade

    To update only APT, run sudo apt install --only-upgrade apt instead. Run apt-cache policy apt again afterwards to confirm the new version.

  3. Update from a network you trust, if you can. The attack depends on someone sitting between you and the mirror. So for this update, avoid public Wi-Fi and proxies you don't control.

  4. Don't forget containers and images. Docker images, VM templates and CI runners based on Debian or Ubuntu have their own copy of APT. Rebuild them from updated base images or update them directly.

  5. Older Ubuntu LTS releases. On Ubuntu 20.04 or older, you need Ubuntu Pro enabled to get the fix. Otherwise, plan an upgrade to a supported release.

If you manage several servers, this is a good time to make sure you can log in to all of them quickly. Our guide to SSH keys and passwordless login covers the setup. As always, keep backups that follow the 3-2-1 rule before you make system changes.

Sources

Liked this guide? Get the next one by email

The best new tutorials and guides, a few times a month. Unsubscribe any time.

We'll email you a link to confirm. See our privacy policy.