Plan this weekVulnerabilities

A flaw in apt (Ubuntu and Debian) could let an attacker install a fake package as root. Update apt now

Ubuntu and Debian published fixes on 4 Nov 2026 for CVE-2026-109518 in apt, the tool that installs software on Debian and Ubuntu servers. An attacker who can change plain-HTTP traffic, or a malicious mirror, could make apt install a package even when its signature check fails, and run code as root. Ubuntu reports no known attacks. Which versions are fixed and what to run.

Updated 5 Nov 2026: see what changed

How urgent

Plan this week

Who is affected

Servers, containers and PCs that use apt on Debian 12 and 13 and Ubuntu 14.04 to 26.10, if they download packages over plain HTTP or from a mirror the attacker controls. Debian 12 and Ubuntu 22.04 LTS and later are affected by default. Older releases are affected only if the download retry setting was changed from 0

What to do

Update apt (sudo apt update, then sudo apt upgrade), and while you do it set retries to zero as Ubuntu recommends (-o Acquire::Retries=0). Check the version afterward, switch your package sources to https:// where your mirror supports it, and rebuild container images that were built before the fix

Published 5 Nov 2026 · Sources last checked 5 Nov 2026No. 55 / 87

Updates, follow-ups and corrections

  1. Update · 5 Nov 2026. First version of the story, based on Ubuntu's CVE page and blog post (4 Nov 2026) and the Debian security tracker, all read directly. Ubuntu's post does not report attacks in the wild. We have not tested the flaw.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On 4 November 2026 Ubuntu and Debian published fixes for CVE-2026-109518, a flaw in apt, the program that downloads and installs software on Debian and Ubuntu systems. Ubuntu rates it High (CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary 4.0 score 7.7) and credits Max Justicz with finding it and reporting it responsibly.

According to Ubuntu and Debian, an attacker who can change the web traffic between your system and the package server, for example on the network path or through a malicious mirror, can trick apt into installing a package that is under the attacker's control even when it fails the signature check. Package install scripts run as root, so the result is code execution with full control of the machine.

What has to be true for it to work

The attack has conditions, and they are worth knowing because they shape your risk:

  • The traffic must be changeable. Ubuntu says HTTPSHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary blocks this, and FTP is not affected.
  • apt must follow redirects and retry a failed download. That depends on the Acquire::Retries setting. If it is 0, the flaw cannot be used.
  • The default for that setting is 3 on Debian 12 and Ubuntu 22.04 LTS and later, so those are affected out of the box. Older releases are affected only if someone changed the setting.
  • Ubuntu says snap packages are not affected.

Ubuntu's post does not report any exploitation in the wild.

Fixed versions

  • Debian 12 (bookworm): apt 2.6.2. Debian 13 (trixie): apt 3.0.4.
  • Ubuntu 22.04 LTS: 2.4.15ubuntu0.1. 24.04 LTS: 2.8.4ubuntu0.1. 26.04 LTS: 3.2.1ubuntu0.1. 26.10: 3.3.3ubuntu0.1.
  • Ubuntu 14.04 to 20.04: fixes are in Ubuntu Pro (ESM) versions.

Ubuntu says systems with unattended upgrades (on by default since Ubuntu 16.04 LTS) should receive the fix automatically within about 24 hours.

What we could and could not confirm

We read Ubuntu's CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary page and blog post and the Debian tracker entry directly. We could not open The Hacker News article (it returned an error), and we did not test the flaw. We do not know of any real attack.

Who is affected

Anyone who installs packages with apt over plain HTTP or from a mirror they do not control: servers, CI machines, laptops and container images built on Debian or Ubuntu. An attacker needs to be on the path or to run the mirror, so a server that only uses HTTPS sources from the official archive is at lower risk, but it should still be updated.

What to do

  1. Update apt. Ubuntu recommends: sudo apt update && sudo apt upgrade -o Acquire::Retries=0. The option turns off retries during the update, which closes the door while you patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary.
  2. Check the version. On Ubuntu, apt list --installed '?source-package(^apt$)' shows it; compare with the list above.
  3. Prefer HTTPS sources. Where your mirror supports it, change http:// to https:// in your sources files. Ubuntu calls this an optional precaution.
  4. Rebuild container images and base images that were built before the fix, and check CI runners.
  5. Know your mirrors. If you use a third-party or internal mirror, check who runs it and that you reach it over HTTPS.

If you build with AI tools

Our advice, not from the advisories: AI-written Dockerfiles often run apt-get install against plain http:// mirrors or pin old base images. Ask your assistant to switch the sources to HTTPS, use a current base image, and rebuild.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks