On this page (7 sections)

On October 29, 2026, the Debian Security Team published DSA-6595-1, a security update for the tor package. The advisory says multiple vulnerabilities were found in Tor that could result in denial of service, and that the stable distribution (trixie) is fixed in version 0.4.9.15-0+deb13u1.

If you run a Tor relay, a bridge, an onion service or any server that has the tor package installed on Debian 13, this update is for you. The advisory is short, so this article also covers what it does and does not tell you, and how to verify and apply the fix.

What Debian announced

The advisory, signed by Moritz Muehlenhoff, describes Tor as a connection-based low-latency anonymous communication system and states that multiple security vulnerabilities were discovered in it. The stated consequence is denial of service, meaning an attacker could make the service stop working or become unavailable.

Debian's recommendation is simple: upgrade your tor packages. For the detailed security status, the advisory points to the Debian security tracker page for tor.

What we do not know yet

The advisory gives very little detail, and only this one primary source is available for the story so far. Treat the following as unconfirmed:

  • CVE identifiers: the advisory lists the CVE ID as not yet available, so no CVSS score or severity rating is known.
  • The exact number of vulnerabilities and which Tor component each affects: the advisory only says "multiple".
  • Whether the flaws can be triggered remotely, and by whom (for example any network client versus a relay peer): not stated.
  • Whether any of them are being exploited: the advisory does not say, and we have no other source.
  • Other Debian releases: the advisory mentions only the stable distribution, trixie.
Check the Debian security tracker page for tor for updates, since CVE identifiers and per-release status may be added there over time.

Who is realistically exposed

A denial of service in Tor matters most to people who depend on a Tor process staying up. That includes operators of public relays and bridges, and website owners who publish an onion service alongside their normal site. A crash or resource exhaustion in the tor daemon would take that service offline, though the advisory does not describe the mechanism.

A server that merely has the tor package installed but is not running it, or a desktop where Tor is used occasionally, has a lower practical exposure. Even so, keeping the package current is cheap and avoids having to reason about it later.

How to check your version

Run this on the Debian host to see the installed and candidate versions of tor. On trixie, you want the installed version to be 0.4.9.15-0+deb13u1 or newer.

Show installed and available tor version (Debian)Shell
apt policy tor

To see whether the daemon is actually running and which version the binary reports, use the following two read-only commands.

Check whether the tor service is active (systemd hosts)Shell
systemctl status tor
Print the version of the tor binaryShell
tor --version

What to do now

  1. Find every Debian host with tor installed, including relays, bridges, onion service hosts and containers built from Debian images.
  2. Run apt policy tor and note any host on trixie below 0.4.9.15-0+deb13u1.
  3. Refresh package lists and upgrade the tor package (commands below).
  4. Restart the tor service if the package upgrade did not already do so, then confirm it is active.
  5. Confirm the new version with tor --version and apt policy tor.
  6. Review the tor logs for errors after the restart and check that your relay or onion service is reachable again.
  7. Rebuild and redeploy any container images that bundle an older tor package.
  8. Watch the Debian security tracker page for tor for CVE identifiers and further details.

This updates only the tor package on a Debian system and leaves other packages at their current versions.

Upgrade only the tor package (Debian, run as root or with sudo)Shell
sudo apt update
sudo apt install --only-upgrade tor
Caution. Restarting tor drops existing circuits and briefly interrupts a relay, bridge or onion service. Do it in a maintenance window if the service has active users, and keep a second instance running if you need continuity.

If the upgrade did not restart the service, this restarts tor and then shows its status, which should read active (running).

Restart tor and confirm it came back (systemd hosts)Shell
sudo systemctl restart tor
systemctl status tor

Debian also supports unattended security updates. If you have not enabled them, consider doing so for hosts that run exposed services, so that advisories like this one are applied without waiting for a manual change window.

Detection and monitoring afterwards

Because the impact is denial of service, the practical signal is availability. Watch for unexpected tor process restarts or crashes in the system journal, and for relay or onion service downtime that you cannot explain.

This read-only command prints the last seven days of tor log entries from the systemd journal; look for repeated restarts or crash messages.

Show recent tor log entries from the journal (systemd hosts)Shell
journalctl -u tor --since "7 days ago" --no-pager

Repeated restarts, out-of-memory kills or crash messages can have many causes and are not proof of attack, but a pattern that starts before you patch and stops afterwards is worth recording.

If you publish a website over an onion address as well as the public web, external uptime checks on both help you notice outages quickly. Webforta Monitor covers uptime, certificate and DNS monitoring for your public site, and the uptime monitoring guide explains what to alert on.

Bottom line

The advisory is brief, but the action is clear: on Debian trixie, upgrade tor to 0.4.9.15-0+deb13u1 or newer, confirm the version, and revisit the Debian security tracker for CVE details once they are published. Until then, exploitation status and severity remain unconfirmed.

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.

  1. [SECURITY] [DSA 6595-1] tor security updatelists.debian.org ·
  • Debian
  • Tor
  • DSA
  • denial of service
  • patching