Blog/Engineering
Engineering

APT Vulnerability CVE-2026-109518: Debian and Ubuntu Fixed apt Versions, How to Update apt First, and a Mirror and Proxy Checklist for Gulf and Egypt Servers

i
iFynx StudioNov 4, 2026 · 9 min read
Rows of rack-mounted servers with blue status lights in a data centre, the kind of Debian and Ubuntu fleet affected by the APT vulnerability

Direct answer: The APT vulnerability CVE-2026-109518 lets an attacker who sits between a Debian or Ubuntu machine and its package server (for example a malicious mirror or proxy) swap a package after APT has verified it, so the attacker’s code runs as root when the package installs. It affects Debian 12+ and Ubuntu 22.04+ in their default settings. The fix is a new apt: 2.6.2 on Debian 12, 3.0.4 on Debian 13, 2.8.4ubuntu0.1 on Ubuntu 24.04, 2.4.15ubuntu0.1 on Ubuntu 22.04. Update apt itself first, then everything else, and rebuild your Docker base images and CI runners. No exploitation has been reported.

Key facts (checked 4 November 2026, 20:17 Asia/Gaza)

  • What: file verification bypass in APT, which the APT developers rate critical (APT-2026-11-01 advisory). Ubuntu rates it High, CVSS 4.0 7.7 (Ubuntu).
  • Who found it: Max Justicz, credited by the APT developers.
  • How, in one line: redirects plus ordinary HTTP errors make APT retry a download, and the retry can overwrite an already-verified file through a reused hard link.
  • Condition: a non-zero Acquire::Retries. The value 3 is the default since APT 2.3.2, so Debian 12 (bookworm) and Ubuntu 22.04 and later are exposed by default.
  • Fixed in Debian: bookworm 2.6.2 (DLA-4880-1), trixie 3.0.4 (DSA-6607-1), sid 3.3.6. Testing (forky) 3.3.5 still vulnerable (Debian tracker).
  • Ubuntu: fixed builds published 4 November; Ubuntu’s CVE page still listed its releases as vulnerable when we checked (Ubuntu).
  • Exploitation: none reported. Workaround: none published. Patch apt.
Rows of rack-mounted servers with blue status lights in a data centre, the kind of Debian and Ubuntu fleet affected by the APT vulnerability
Linux servers in a data centre. Most Debian and Ubuntu fleets install packages through APT. Photo: Victor Grigas via Wikimedia Commons, CC BY-SA 3.0, cropped.

APT is the tool almost every Debian and Ubuntu server uses to install software, and it runs as root. On 4 November 2026 the APT developers, Debian and Ubuntu published fixes for CVE-2026-109518, a flaw that lets someone on the network path replace a package after APT has checked its signature and hash. Phoronix and The Hacker News picked it up within hours, and posts about it on X rose from a handful an hour to about 80 an hour by the evening.

This matters in the Gulf and Egypt because so much of the region’s hosting, bank and fintech back ends, and CI runners are Ubuntu or Debian, and many of them pull packages through a local mirror or a corporate proxy. That is exactly the position this flaw needs. We explain what is affected, which apt version fixes each release, the order to patch in, and a mirror and proxy checklist. As always, there is no attack method here.

What is the APT vulnerability CVE-2026-109518?

In the words of the APT developers’ advisory, a remote attacker could “bypass verification of downloaded packages using redirects and standard transient HTTP server errors that cause APT to retry downloads, leading APT to override existing hardlinks with a chosen payload.” Because .deb packages are installed with root privileges, that means potential remote code execution.

Ubuntu’s description names the attacker: an on-path party who can manipulate traffic between the APT client and the archive, including a malicious mirror or proxy. The attack is triggered by a package install, needs the client to follow redirects and retry, and needs Acquire::Retries above zero.

As debs are installed with root privileges, this provides the potential for remote code execution.

Julian Andres Klode, APT developer, APT-2026-11-01 advisory, 4 November 2026

Which apt version fixes CVE-2026-109518?

ReleaseFixed apt versionStatus (4 Nov)
Debian 13 trixie3.0.4DSA-6607-1, fixed
Debian 12 bookworm2.6.2DLA-4880-1, fixed
Debian unstable (sid)3.3.6fixed
Debian testing (forky)3.3.5 still vulnerablenot fixed yet
Debian 11 bullseye2.2.5 (APT branch fix)via LTS/eLTS channels
Ubuntu 26.103.3.3ubuntu0.1builds pushed; tracker lagging
Ubuntu 26.04 LTS3.2.1ubuntu0.1builds pushed; tracker lagging
Ubuntu 24.04 LTS2.8.4ubuntu0.1builds pushed; tracker lagging
Ubuntu 22.04 LTS2.4.15ubuntu0.1builds pushed; tracker lagging
Ubuntu 14.04 trusty1.0.1ubuntu2.24Ubuntu Pro only

Debian versions come from the Debian security tracker. The APT developers also released branch fixes for older series: 1.2.36, 1.4.12, 1.6.19, 1.8.2.4, 2.0.12, 2.2.5, 2.4.15, 2.6.2, 2.8.4, 3.0.4 and 3.2.1. The Ubuntu versions above are the Ubuntu builds of those fixes. Check apt-cache policy apt on your own machine against your release’s security pocket.

Unpatched right now

Debian testing (forky) was still on vulnerable apt 3.3.5 when we checked, and Ubuntu’s CVE page still marked its releases vulnerable even though fixed builds had been pushed. If a host reports no new apt, re-run apt-get update later and check again.

How to update apt first, then the rest

Update apt as its own step. The fixed client then handles every later download in the same maintenance window. These commands are read-only checks plus the standard upgrade; run them from a mirror you trust.

# 1) What apt version is installed, and is retry on?
apt-cache policy apt | head -3
apt-config dump | grep -i 'Acquire::Retries'

# 2) Update apt itself first, then everything else
sudo apt-get update
sudo apt-get install --only-upgrade apt
apt-cache policy apt | head -3      # confirm the fixed version
sudo apt-get upgrade

# 3) Fleet check (Ansible example)
ansible all -b -m shell -a "dpkg-query -W -f='\${Version}' apt"

With AWS Systems Manager, run the same --only-upgrade apt command as a Run Command document before your normal patch baseline. With Ansible, use apt: name=apt state=latest only_upgrade=yes as the first task. If you already work through our Linux kernel CVE-2026-98432 checklist, put apt ahead of the kernel in the same window.

Does HTTPS protect you? Do not assume it

Neither Debian nor Ubuntu says HTTPS removes the risk, so we will not either. The attacker described is on the path, and a malicious mirror or proxy can sit there whatever the transport. A TLS-inspecting corporate proxy, common in Gulf banks, terminates and re-creates the connection, so it is on the path too. Patch apt on every host, HTTPS or not.

Docker images and CI runners: rebuild them

Containers are where this bites quietly. Every RUN apt-get install in a Dockerfile runs as root inside the build, often on shared CI runners with network access through a cache or proxy. A patched host does not patch the apt inside an image.

  • Pull refreshed ubuntu:24.04, ubuntu:22.04, debian:bookworm and debian:trixie bases, then rebuild and redeploy.
  • Add apt-get install --only-upgrade apt before other installs in long-lived Dockerfiles until the bases catch up.
  • Rebuild self-hosted GitHub Actions and GitLab runner images; hosted runners are refreshed by the provider, so check their image notes.
  • Scan registries for images built before 4 November that still run apt-get at start-up.

Mirror and proxy checklist for Gulf and Egypt servers

  1. Inventory: list every Debian/Ubuntu host, container base image and CI runner image; record the installed apt version.
  2. Update apt first on each host, confirm the fixed version, then run the normal upgrade.
  3. Patch order: internet-facing and build systems first (CI runners, image builders, bastions), then app servers, then the rest.
  4. Rebuild images: pull fresh ubuntu:24.04 / debian:bookworm / debian:trixie bases; rebuild and redeploy; refresh self-hosted GitHub/GitLab runner AMIs.
  5. Mirrors: use only official mirrors or an internal mirror you control; remove unknown third-party mirrors from sources.list and .sources files.
  6. Proxies: review apt-cacher-ng, Squid or TLS-inspecting proxies on the path; restrict who can administer them; log changes.
  7. Repo keys: keep signed-by= per repository so a third-party key cannot sign packages for the main archive.
  8. Debian testing: do not run forky on production; if you must, watch the tracker for 3.3.6+.
  9. Evidence: keep the before/after version report for the regulator or auditor.

Patch timelines: NCA, CBUAE and Egypt’s FRA

A root-level flaw on core servers falls under your critical-patch process. In Saudi Arabia, the NCA Essential Cybersecurity Controls require documented vulnerability and patch management with defined timelines, and most bank and government policies treat critical items in days, not weeks. In the UAE, banks follow the CBUAE rulebook on technology risk, which expects timely patching and evidence. In Egypt, non-bank fintechs supervised by the Financial Regulatory Authority are expected to patch and keep records. Whatever your exact SLA, record the date you learned of CVE-2026-109518 (4 November), the date apt was updated, and the image rebuilds.

Node.js side box: next week’s patch

Separately, the Node.js project has pre-announced high-severity security releases for Node.js 22, 24 and 26 on or after 11 November 2026 (Node.js security blog). If your Node apps run on Debian or Ubuntu images, plan one rebuild that picks up both the apt fix now and the Node fix next week. See our Brotli Node2Shell checklist for the last Node round.

FAQ

Is my Ubuntu or Debian server affected by CVE-2026-109518?

Probably, if it runs Debian 12 or later or Ubuntu 22.04 or later and has not installed the fixed apt yet. These releases set Acquire::Retries to 3 by default, which the flaw needs. Older releases are only exposed if someone turned retries on. Run apt-cache policy apt and compare with the fixed versions table.

Which apt version fixes CVE-2026-109518?

Debian 12: 2.6.2. Debian 13: 3.0.4. Debian unstable: 3.3.6. Ubuntu 24.04: 2.8.4ubuntu0.1. Ubuntu 22.04: 2.4.15ubuntu0.1. Ubuntu 26.04: 3.2.1ubuntu0.1. Ubuntu 26.10: 3.3.3ubuntu0.1. Debian testing (forky) had no fix when we checked.

How do I update apt safely?

Upgrade apt on its own first with sudo apt-get install --only-upgrade apt, confirm the new version, then run the rest of your upgrade. That way every later download is handled by the fixed client. Do it from a mirror you trust.

Does an HTTPS mirror protect me?

Do not assume so. The Debian and Ubuntu advisories describe an on-path attacker, including a malicious mirror or proxy, and do not say HTTPS removes the risk. A compromised HTTPS mirror or a TLS-inspecting corporate proxy is still on the path. Patch apt regardless of transport.

Do Docker images and CI runners need rebuilds?

Yes. Base images such as ubuntu:24.04 and debian:bookworm ship apt inside the image, and every apt-get install in a Dockerfile or CI job runs as root. Pull refreshed base images, rebuild, and update self-hosted runner images.

What about Debian 11 and Ubuntu 20.04?

In a default configuration they are not affected, because retries were not on by default before APT 2.3.2. If your scripts or images set Acquire::Retries, they are exposed. The APT developers released branch fixes (2.2.5 for Debian 11, 2.0.12 for the 2.0 series used by Ubuntu 20.04); install them through LTS, eLTS or Ubuntu Pro.

Is CVE-2026-109518 being exploited?

No exploitation has been reported as of our check. No workaround has been published either, so the fix is the upgrade.

Sources

Related reading

*Published 4 November 2026, 20:17 Asia/Gaza by iFynx. Times are Asia/Gaza (UTC+2). We will add a dated update if exploitation is reported or Ubuntu’s tracker changes.*