On this page (7 sections)
On 17 November 2026 Ubuntu published USN-8979-2 for the Deluge BitTorrent client. It says the fixes shipped earlier in USN-8979-1 were never applied in the Ubuntu 16.04 LTS package because of a packaging error, and this notice corrects that.
If you run Deluge with its web UI on Ubuntu 16.04 LTS (for example on a seedbox or a home server reachable over a network), you should update the package and restart the service. The two underlying flaws date from 2017, but a system that never received the fix is still exposed.
What happened
Ubuntu first released USN-8979-1 to fix Deluge vulnerabilities. According to the follow-up notice, a packaging error meant the fixes were not actually applied in the Ubuntu 16.04 LTS build. USN-8979-2 fixes that problem, so anyone who installed the first update on 16.04 may still have been running vulnerable code.
The notice covers two issues in the Deluge web UI. Ubuntu describes them as a missing cross-site request forgery protection and incorrect handling of certain requests that could allow arbitrary file reads.
Technical details in plain terms
CVE-2017-7178: cross-site request forgery
CSRF (CWE-352) means the application cannot reliably tell whether a request was deliberately made by the logged-in user or triggered by another site. Per the GitHub advisory, Deluge before 1.3.14 was affected. The described attack needs a victim to download, install and enable a crafted plugin that runs an arbitrary program from its initialization file. Ubuntu summarizes the impact as possible execution of arbitrary code after a user is tricked into installing a malicious plugin. The CVSS v3.1 vector in the advisory lists user interaction as required, which fits that description.
CVE-2017-9031: directory traversal
Directory traversal (CWE-22) happens when input is used to build a file path without blocking elements that escape the intended folder. The advisory says the web UI before Deluge 1.3.15 mishandles a request in which the render file name is not associated with any template file. Ubuntu says a remote attacker could possibly read arbitrary files. The CVSS v3.0 vector in the advisory shows network access, low complexity, no privileges required and no user interaction, which is consistent with the 9.8 score.
Who is affected
- Ubuntu 16.04 LTS systems with the deluge-common or deluge-web packages installed, per USN-8979-2.
- Setups where the Deluge web UI is running and reachable by other machines.
- Servers where an earlier USN-8979-1 update was applied on 16.04 and assumed to be sufficient. Ubuntu states those fixes were not actually applied.
The research does not list affected or fixed versions for other Ubuntu releases in this notice. Systems not running the web UI have less exposure to these two web UI flaws, though updating is still sensible.
How to check your exposure
This read-only command shows the installed Deluge package versions on Ubuntu or Debian. On 16.04 LTS, look for 1.3.12-1ubuntu1+esm2; an older version string means the fix is missing.
dpkg -l | grep delugeThis command lists running Deluge processes, so you can see whether the web UI is active.
ps aux | grep -i delugeWhat to do now
- Run a standard system update so the deluge-common and deluge-web packages move to 1.3.12-1ubuntu1+esm2 on Ubuntu 16.04 LTS.
- Restart Deluge after the update. Ubuntu states a restart is needed to make all the necessary changes take effect.
- Re-run the version check and confirm the new package version is installed.
- Restrict access to the Deluge web UI to trusted networks, for example behind a VPN or a firewall rule, rather than exposing it to the internet.
- Review installed Deluge plugins and remove any you do not recognize, since the CSRF issue is described as a route to installing a malicious plugin.
- If the web UI was reachable and unpatched, consider changing credentials and checking the host for unexpected files, processes or plugins.
This command refreshes the package lists and upgrades only the two Deluge packages. Run it on the affected Ubuntu 16.04 LTS host, then confirm the version with the check above.
sudo apt update && sudo apt install --only-upgrade deluge-common deluge-webDetection and monitoring
Because directory traversal is about reading files, signs of abuse would mostly be unusual requests in web server or reverse proxy logs in front of Deluge, if you have one. Look for requests to the web UI from unfamiliar addresses and for unexpected plugin installs or enabled plugins in the Deluge configuration. No indicators of compromise are given in the research, so treat these as general hygiene rather than confirmed signatures.
If your Deluge web UI sits behind a public hostname, keep its certificate and DNS under watch, for example with Webforta Monitor, and review the security headers of any proxy in front of it. For a wider routine, see the small business website security guide.
Timeline
| Date | Event |
|---|---|
| 2017-03-18 | CVE-2017-7178 published by NVD (Deluge before 1.3.14) |
| 2017-05-17 | CVE-2017-9031 published by NVD (Deluge before 1.3.15) |
| 2026-11-17 | Ubuntu publishes USN-8979-2 after a packaging error left USN-8979-1 fixes unapplied on 16.04 LTS |
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.
