Tailscale ships the fix for its SSH root-access bugs
Version 1.104.4 closes the privilege-escalation flaws the Tailworm report disclosed two days ago, with four bulletins but no CVEs and no sign of exploitation in the wild.
Tailscale published “SSH: Findings and fixes” today, confirming the privilege-escalation bugs from the Tailworm report and shipping version 1.104.4 to close them. The post says its teams started investigating on 23 October, before the report went public, after concerns surfaced on social media.
Four issues are covered across separate bulletins, TS-2026-014 through TS-2026-017. The worst, TS-2026-014, let an authenticated SSH peer use Unix-socket forwarding to reach root-only sockets such as the Docker socket or tailscaled’s own local API, effectively escalating to root on a machine it only had limited access to. The others cover a memory-exhaustion bug in SSH session handling and two issues in tailscale serve. None have CVE identifiers yet. Tailscale says there’s no evidence of exploitation outside the lab demonstration in the original report, and an attacker still needed an already-authorised device inside the tailnet to use any of this.
Why it matters: when we covered Tailworm two days ago, the advice was policy workarounds because there was no patch. Now there is one: if you run Tailscale SSH, updating to 1.104.4 closes the issue outright rather than relying on access-rule restrictions.
The caveat: if you can’t upgrade immediately, Tailscale recommends turning on SSH check mode, which adds a second authentication step before granting a session.