On this page (6 sections)
On November 4, 2026, the Debian security team published DSA-6607-1, a security update for apt, the package manager used to install and update software on Debian systems. It addresses CVE-2026-109518, a flaw that could let an attacker positioned on the network replace a package after it had already been verified.
Anyone who runs Debian servers should care, including hosting administrators and agencies that manage web servers. The fix is a routine package update, and it is worth applying soon because the affected tool is the one that installs everything else.
What happened
Debian's advisory says Max Justicz found a vulnerability in apt. When an HTTP redirect gives two different package downloads the same URI, apt can merge those downloads. Separately, the advisory describes improper file handling when an HTTP download is resumed. Together, it says, this lets a man-in-the-middle attacker replace a package after verification, which results in code running as root.
The same update also addresses several out-of-bounds access issues, according to the advisory. It does not assign them identifiers or describe their impact, so treat them as additional reasons to update rather than as separate known threats.
Why this weakness matters
APT normally protects you by verifying a package against signed repository metadata before installing it. That check is only useful if the file installed is the same file that was checked. The flaw described here is about that gap: if a package is swapped after verification, the check has already passed and the replaced file is installed anyway.
Because package installation runs as root, a successful swap means full control of the machine. The attacker does need to be a man-in-the-middle, meaning able to intercept or alter traffic between the server and its package source. That is a real condition, not a remote one-click attack, but it is plausible on networks you do not fully control. The advisory describes the problem in terms of HTTP downloads and does not say whether HTTPS mirrors change the risk, so do not assume they remove it.
Who is affected
The advisory names the stable distribution, trixie, and says the problem is fixed in apt 3.0.4. It does not list other Debian releases or say which older apt versions are vulnerable. For other releases, check the Debian security tracker page for apt that the advisory points to.
Because the advisory does not narrow the scope further, treat any Debian host that runs apt as in scope, including build servers and container images that run apt during builds.
How to check your exposure
This read-only command shows the installed apt version and the candidate version available from your configured repositories. On trixie, you want the installed version to be 3.0.4 or newer.
apt-cache policy aptThis command prints just the installed version string, useful in scripts across many servers.
dpkg-query -W -f='${Version}\n' aptIf you run releases other than trixie, compare your version against the fixed version in the Debian security tracker rather than assuming 3.0.4 applies, since the advisory only states that number for trixie.
What to do now
- Check the installed apt version on each Debian host with the command above.
- Refresh package lists and upgrade apt using the commands below.
- Confirm apt reports version 3.0.4 or newer on trixie.
- Rebuild container images and golden images that bake in an older apt.
- Prefer trusted networks for package updates until every host is patched.
- Review recently installed packages on exposed hosts for anything unexpected.
This updates the package index and then upgrades only apt, so you can apply the fix without upgrading everything else. Run it on a Debian host with sudo or as root.
sudo apt update
sudo apt install --only-upgrade aptAfter the upgrade, run the version check again and confirm the result. If you manage many servers, apply the same update through your configuration management or patching tool and verify the version afterwards.
Detection and monitoring
The advisory does not describe indicators of compromise, so there is no specific signature to hunt for. Practical checks are general ones: review apt history for installs you did not expect, and compare installed package files against known-good checksums.
This read-only command checks installed files against the checksums recorded in their packages. It needs the debsums package, which is not installed by default, and any files it reports as changed deserve a closer look.
sudo debsums -sThis opens the apt history log so you can spot installs or upgrades you cannot account for.
less /var/log/apt/history.logFor public-facing sites, a patched package manager is only one layer. You can watch certificate and DNS changes with Webforta Monitor, and our guide on what to do if a website is hacked covers next steps if you find signs of tampering.
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.
