Debian has patched CVE-2026-109518, a flaw that can let an attacker replace a downloaded package after APT has verified it. APT installs packages with root privileges, so successful substitution can lead to code execution with full system control. Debian’s November 4 advisory credits researcher Max Justicz and recommends updating APT.
Evidence status: a disclosed vulnerability with vendor-provided fixes. The Debian advisory and maintainer disclosure reviewed here report no exploitation in the wild. Their description of possible root access is an impact statement, not evidence of compromised machines.
Redirects and retries break the verified-file boundary
APT can merge two package downloads after an HTTP redirect gives them the same address. Incorrect file handling when resuming a download can then replace already verified content. The failure is in preserving the verified file through installation; it does not require breaking a signing key.
Julian Andres Klode’s maintainer disclosure identifies an important prerequisite: Acquire::Retries must be enabled. This has been the default since APT 2.3.2, but scripts can enable retries on older releases too.
The attack also requires control over the relevant download responses, such as a man-in-the-middle position on HTTP traffic. An arbitrary website visit alone is not the described attack. Older APT versions cannot be dismissed solely because their retry default differs.
Install the security update for the actual distribution
Debian’s security tracker lists these branch-specific repairs:
| Debian release | Vulnerable version shown in tracker | Fixed security version |
|---|---|---|
| 13, Trixie | 3.0.3 | 3.0.4 |
| 12, Bookworm | 2.6.1 | 2.6.2 |
These are security baselines, not instructions to downgrade a newer package. The tracker now lists 3.3.6 in unstable (sid) as fixed, while testing (forky) still shows 3.3.5 as vulnerable. Check the actual distribution and channel; a fixed unstable package does not establish that testing or every mirror has received it.
Use the distribution’s supported security-update process and confirm the resulting installed APT version. Include container base images, build images and less-used hosts in the normal update inventory. A newer host package does not replace the package manager inside an existing image.
Klode says updates for affected Ubuntu and Ubuntu Pro channels are also being released. Their package versions differ from Debian’s. Ubuntu users should follow their release’s advisory rather than install a Debian package or assume the Debian version table applies.
Because the vulnerable component retrieves its own update, the download path deserves attention. Use a trusted update route and seek distribution guidance if that route may be intercepted. Keep package authentication enabled; the disclosures do not recommend bypassing verification to obtain the fix.
What the thread adds
The larger Hacker News discussion, linked from the newer submission, raises two practical questions. hypfer asks whether Bookworm has a fix; basilikum points to the tracker. It now lists 2.6.2 in Bookworm’s security channel, so the earlier uncertainty should not become standing advice.
vesinisa initially questions Ubuntu’s exposure. kpcyrd replies with Klode’s disclosure, which explicitly includes Ubuntu update channels. That first-party source supports the correction without relying on a commenter’s identity.
flotzam asks how to obtain the repair securely. Replies suggest transport changes and configuration workarounds, but the thread supplies no verified, complete recovery procedure. Those suggestions should not substitute for the distribution’s instructions.
From a 57-comment thread, in HN’s own order.
Caveat: these are fresh Debian disclosures; other distributions’ exact fixed packages and any real-world exploitation remain unverified here.
Update — November 4, 2026, 9:43 p.m. EST
The Debian tracker now lists sid’s package version as 3.3.6, fixed. The earlier snapshot still showed 3.3.5 there. Forky remains listed as vulnerable at 3.3.5; Bookworm and Trixie’s security fixes are unchanged. This changes branch availability, not the evidence of exploitation.