On this page (7 sections)

Ubuntu published security notice USN-8996-1 on 4 November 2026. It covers a weakness in APT, the package front-end used on every supported Ubuntu release. Ubuntu's notice says a remote on-path attacker could possibly trick APT into installing an unverified package and gain remote code execution with root privileges.

If you run Ubuntu servers, build hosts, containers based on Ubuntu images or shared hosting machines, this applies to you. The fix ships as a normal package update, so the real work is making sure it reaches every host.

What happened

Ubuntu credits researcher Max Justicz with finding that APT handled hard links incorrectly when it met redirects and retried package downloads. The notice summarizes the impact as APT being made to install unverified packages and run programs as an administrator.

The notice is brief. It does not explain how the attack works, whether an exploit exists, or how severe the issue is rated. Only one publisher (Ubuntu itself) covers this story so far, so anything beyond the notice should be treated as unconfirmed.

Why it matters

APT exists to make sure only verified packages get installed. A flaw that lets an unverified package through undermines that guarantee, and because APT normally runs as root, the notice says the outcome could be code execution with root privileges.

Ubuntu describes the attacker as a remote on-path attacker, meaning someone positioned to intercept or alter traffic between a machine and its package source. The notice gives no further detail on other conditions or attack routes, and no guidance on which setups carry less risk. The safest reading is to update every Ubuntu host.

The following list is our own general reasoning about where an on-path position is more plausible. It is not taken from the notice:

  • Servers or workstations on shared, untrusted or compromised networks.
  • Machines that reach package sources through mirrors or proxies you do not control.
  • Build systems and CI runners that run apt update and apt install automatically.
  • Hosting environments where many customers share network paths.

Fixed package versions

Ubuntu lists these fixed APT versions per release. For 20.04 LTS and older, the fix is available through Ubuntu Pro (for 16.04 LTS and 14.04 LTS, through the Legacy Support add-on).

Fixed APT versions per Ubuntu release (source: USN-8996-1)
Ubuntu releaseFixed apt versionAccess
26.103.3.3ubuntu0.1Standard updates
26.04 LTS3.2.1ubuntu0.1Standard updates
24.04 LTS2.8.4ubuntu0.1Standard updates
22.04 LTS2.4.15ubuntu0.1Standard updates
20.04 LTS2.0.12+esm1Ubuntu Pro
18.04 LTS1.6.19+esm1Ubuntu Pro
16.04 LTS1.2.36+esm1Ubuntu Pro (Legacy Support add-on)
14.04 LTS1.0.1ubuntu2.24+esm4Ubuntu Pro (Legacy Support add-on)

How to check if you are exposed

This read-only command shows the installed and candidate versions of APT. Run it on each Ubuntu host and compare the installed version with the table above. If the installed version is older than the fixed one, the host still needs the update.

Show the installed and available apt version (Ubuntu)Shell
apt-cache policy apt

To see which Ubuntu release a host runs, so you know which row of the table applies, use this read-only command:

Show the Ubuntu release (Ubuntu)Shell
lsb_release -a

What to do now

Ubuntu says that in general a standard system update will make all the necessary changes.

Caution. This is our general precaution, not something stated in the notice: on critical servers, upgrade during a planned maintenance window and have a recent backup or snapshot first. On unattended build machines, confirm no job is mid-install before upgrading.

This refreshes the package lists and upgrades only the apt package on a host. Run it with sudo, then re-run apt-cache policy apt to confirm the installed version matches the fixed one for your release.

Update the package lists and upgrade only apt (Ubuntu)Shell
sudo apt update
sudo apt install --only-upgrade apt

If you prefer a full standard update, as Ubuntu describes, this upgrades all pending packages:

Apply all pending updates (Ubuntu)Shell
sudo apt update
sudo apt upgrade
  1. List every Ubuntu host you run, including build servers, containers and staging machines.
  2. Run apt-cache policy apt on each and compare with the fixed versions above.
  3. Apply the update and re-check the version afterwards.
  4. For Ubuntu 20.04 LTS and older, enable Ubuntu Pro to receive the fix, or plan an upgrade to a supported release.
  5. Rebuild container images and VM templates that bundle an older apt.
  6. Update every host rather than only those you judge to be exposed, since the notice gives no guidance on reduced risk.
Tip. Ubuntu notes that Ubuntu Pro is free for up to five machines, which may cover a few older 20.04 or 18.04 hosts while you plan a migration.

Monitoring after the update

The notice lists no indicators of compromise, so there is nothing specific to search for. General hygiene still applies: review recent apt history for packages you did not expect, and watch for unexplained new users, services or outbound connections. This read-only command prints the install and upgrade entries from the APT history log.

Review recent package installs and upgrades (Debian/Ubuntu)Shell
grep -E 'Start-Date|Commandline|Install:|Upgrade:' /var/log/apt/history.log

For public-facing sites, patching the operating system is one layer. The Webforta security scanner can check your verified websites from the outside, and certificate and DNS monitoring helps you notice unexpected changes to the endpoints your servers depend on. Neither replaces applying the Ubuntu update. For broader hygiene, see website security for small business.

What we do not know yet

  • No CVSS score or severity rating is given in the notice.
  • Whether the flaw is being exploited in the wild is not stated.
  • Technical details of the attack, and whether non-Ubuntu distributions are affected, are not covered by the notice.
  • Only the Ubuntu notice covers this so far, so there is no independent confirmation yet.

We will update this article if Ubuntu or other sources publish more detail.

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-8996-1: APT vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • APT
  • USN
  • Linux
  • package management
  • patching