VulnSocial
  • Dashboard
  • Blog
VulnSocial

Vulnerability intelligence from social chatter. CVEs ranked by what attackers and researchers are amplifying right now.

Product

  • Dashboard
  • What to fix first
  • How it works

Resources

  • CVE blog

Legal

  • Privacy policy
  • Terms of service

© 2026 VulnSocial. All rights reserved.

Data refreshed daily · AI-classified social signal

  • Home
  • Fix first
  • Blog
← Back to blog

CVE-2026-109518 – High-Severity Root RCE in APT Package Manager on Debian and Ubuntu

TL;DR

  • CVE-2026-109518 is a High severity flaw (CVSS 4.0: 7.7) in apt, the package manager used by Debian, Ubuntu, and derivative Linux distributions.
  • An on-path attacker — a malicious mirror, rogue proxy, or network man-in-the-middle — can swap a package after verification and achieve remote code execution as root during a routine apt install or apt upgrade.
  • Default configurations of Debian 12+ and Ubuntu 22.04+ are in scope because Acquire::Retries defaults to 3; older releases are unaffected by default.
  • There is no workaround: the only reliable fix is to update apt now (Debian 13: apt 3.0.4; Ubuntu: see USN-8996-1).

Overview

CVE-2026-109518 is a package-verification bypass in apt(1), discovered and responsibly disclosed by researcher Max Justicz and patched via DSA 6607-1 and USN-8996-1 on 4 November 2026. It undermines the trust model of the entire Debian/Ubuntu software supply chain: signature checks are defeated not by breaking cryptography, but by racing the download pipeline so the file apt verifies is not the file it installs.

Why it matters: apt is the trust anchor for every Debian-based host — servers, CI runners, containers, workstations. A single package operation over a manipulated network path is enough for root-level compromise, and no confirmed in-the-wild exploitation has been reported yet. This is a patch-now-before-exploitation window.


Technical details

The bug sits in apt's downloader, at the intersection of three behaviors:

  1. Hard-link reuse in the partial-download store.
  2. Redirect following during HTTP acquisition.
  3. Retry logic — exploitation requires a non-zero Acquire::Retries, which has defaulted to 3 since Debian 12 (bookworm) and Ubuntu 22.04 LTS (Jammy Jellyfish).

When a redirect causes two different downloads to resolve to the same address, apt can merge or resume them into the same file via hard links. An on-path attacker can then alter the package file after its integrity check, so the client installs an attacker-controlled, unverified .deb with root privileges. The CWE mapping reflects this: CWE-367 (time-of-check/time-of-use race) alongside CWE-62.

The upstream fix is famously small — per the Debian changelog, four words: 'Open target files exclusively.' First patched release: apt 3.0.4 in Debian 13 security updates.

Trigger preconditions, in short:

  • Client follows HTTP redirects during acquisition.
  • Acquire::Retries is non-zero (default 3 on bookworm/jammy and newer).
  • A package install or upgrade runs (the UI:P in the CVSS vector).

Severity and impact

AttributeValue
CVECVE-2026-109518
SeverityHigh
ScoreCVSS 4.0: 7.7 (CNA: Ubuntu)
VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CWECWE-367, CWE-62
CISA KEVNot listed

The vector says it plainly: network-adjacent, low complexity, no privileges required, high impact on confidentiality, integrity, and availability of the vulnerable system — gated only by a user running an apt operation. No scope change; the blast radius is the local root account.

Threat activity so far. The CVE drew ~156 mentions across security channels in its first 9 days, dominated by patch guidance (47 of 65 day-one posts). A handful of posts flagged active exploitation on Nov 4–5 and Nov 7, but no advisory confirms in-the-wild attacks, no public exploit tool has been released, and only a few early PoC references surfaced. Treat those flags as unconfirmed — and watch the live signal timeline on the VulnSocial CVE page for changes. #CVE2026109518


Affected products

  • Debian 12 (bookworm) and newer, including Debian 13 — fixed in apt 3.0.4 via DSA 6607-1.
  • Ubuntu 22.04 LTS (Jammy Jellyfish) and newer — see USN-8996-1 for per-release fixed versions.
  • Derivatives that inherit the default Acquire::Retries=3.

Older releases are unaffected in a default configuration (retries default to 0), but any host with a non-zero Acquire::Retries should assume exposure. For the full list of affected products and versions, see the CVE page.


Actionable insights: what defenders should do now

  • Patch first, audit second. The advisories offer no workaround; configuration tweaks are not a substitute. Any host that ran apt install/apt upgrade over an untrusted network (public Wi-Fi, shared cloud LAN, third-party proxy) is a candidate for review.
  • Check your mirrors and proxies. Inventory sources.list entries for http:// mirrors, unexpected proxy settings, and redirect behavior. Prefer https:// archives and pin trusted mirrors.
  • Verify package integrity on exposed hosts: dpkg -V (or debsums -c where available), plus a review of /var/log/apt/term.log and /var/log/dpkg.log for installs you did not initiate.
  • Hunt for persistence: new systemd units, cron jobs, authorized_keys, and apt hooks under /etc/apt/apt.conf.d/ are where a root-level implant would land.
  • Rebuild, don't clean, if compromise is confirmed — a swapped .deb means the base image is untrusted.

Remediation and mitigation

  1. Update apt immediately:

    sudo apt-get update && sudo apt-get install --only-upgrade apt
    
  2. Confirm the fixed version (Debian 13 ships apt 3.0.4; match the version in USN-8996-1 for your Ubuntu release):

    apt --version
    
  3. Pull remaining security updates and reboot if a kernel or libc package moved:

    sudo apt-get full-upgrade
    
  4. Audit the host for compromise (logs, package integrity, persistence) as above; if tampering is suspected, rebuild from a known-good image and rotate credentials stored on the host.

  5. Harden the update path: HTTPS mirrors, pinned sources, egress-controlled proxies, and alerting on unexpected apt activity.

  6. Follow up on exploitation signals and advisory updates via the live CVE page.


Bottom line

CVE-2026-109518 is a High severity (CVSS 4.0 7.7) root-RCE flaw in the apt package manager that turns a manipulated network path into full system compromise on default Debian 12+ / Ubuntu 22.04+ configurations. No attacks are confirmed and no workaround exists — the only effective remediation is to patch apt now, then audit hosts that updated over untrusted networks.

References

DSA 6607-1 (Debian Security Advisory)

https://lists.debian.org/debian-security-announce/2026/msg00526.html

USN-8996-1 (Ubuntu Security Notice)

https://ubuntu.com/security/notices/USN-8996-1

oss-security disclosure thread

http://www.openwall.com/lists/oss-security/2026/11/04/12

Debian LTS announcement

https://lists.debian.org/debian-lts-announce/2026/11/msg00004.html

#CVE2026109518 #LinuxSecurity #Debian #Ubuntu #SupplyChain #RCE #PatchNow