'Tailworm': 11 unpatched Tailscale SSH flaws led lab attackers to root access
Eleven unpatched Tailscale SSH findings let a lab attack chain reach root on servers — and on Headscale, every SSH grant should be treated as root.

The News
Security researcher Erica Windisch of Cyberdione Labs published 'Tailworm' on October 25, 2026: eleven unpatched findings in Tailscale SSH. In the lab, with Tailscale SSH port forwarding allowed — port forwarding is a setting that lets network traffic pass through one machine to reach another — and with an attacker already controlling one permitted device, the attack chain reached root, the highest level of control, on reachable servers. One path involved a root-level process connecting to a root-only socket, a restricted communication channel meant only for the system administrator; in another chain, the attacker captured a device-enrolment key, the credential used to register a new device on the network. No CVE number, security bulletin or fixed version had been issued at publication. A CVE is the standard public ID for a confirmed vulnerability; none had been assigned.
Tailscale acknowledged the report and said it was working on fixes, but it was not recommending that everyone disable Tailscale SSH. That distinction matters: the vendor's position, as reported, is that the findings are real enough to fix but not so urgent that every user must switch the feature off immediately. The report's warning is sharper for one group in particular: Headscale version 0.29.5, an open-source alternative server for Tailscale networks, cannot disable port forwarding, so the report says every SSH grant there should be treated as root — in plain terms, assume anyone given SSH access could gain full control.
For the wider security industry, Tailworm is a reminder that remote-access tools are high-value targets precisely because they are trusted. A tool designed to let administrators reach every server in a network becomes, if it has flaws, a single route to all of them. Tailscale is private, so Zscaler (ZS) is named here only as a public read-through — a listed network-security peer — not as a company involved in the findings.
A remote-access tool is a master key — its flaws open every door at once.
Why It Matters
The first reason this matters is what Tailscale SSH is for. Remote-access tools exist so administrators can reach servers from anywhere, which means they are deliberately given broad trust across a network. A flaw in an ordinary app affects that app; a flaw in a remote-access tool can affect every server the tool can reach. That concentration of trust is why eleven findings in one such tool, even with preconditions, lands harder than eleven findings in eleven unrelated apps.
The second reason is the precondition trap. It is tempting to dismiss Tailworm because the attacker must already control a permitted device. In practice, compromising one laptop is the most common first step in real intrusions, through phishing or malware. Security thinking therefore treats 'attacker already has one device' not as a rare edge case but as the expected starting point, and judges a chain by where it ends. Here it ends at root, the highest level of control, which is why the lab result is severe despite its conditions.
The third reason is the Headscale asymmetry. Most Tailscale users can consider disabling port forwarding while fixes are prepared; Headscale 0.29.5 users cannot — that version has no switch for it. The report's advice for them — treat every SSH grant as root — reframes access decisions: granting SSH access on such a server is, until a fix arrives, effectively granting full control. That is a practical warning administrators can act on today, before any patch exists.
Analyst's Take
The verdict is Bearish, because eleven unpatched findings in a trusted remote-access tool, with a lab-demonstrated path to root, is a serious disclosure even with its conditions attached. The mitigating facts are real: the attacker must already control a permitted device, and port forwarding must be allowed. That is not a drive-by attack on strangers. But once those conditions hold — and in real networks, a single compromised laptop is a common starting point — the chain ends at full control of reachable servers, including, in one case, capturing the key used to enrol new devices. An unpatched, unnumbered set of findings in a tool built to reach everything is the wrong combination, and Headscale users cannot even switch the risky setting off.
For administrators, the practical read is narrow and urgent: check whether Tailscale SSH port forwarding is enabled in your network, who holds SSH grants, and whether any Headscale 0.29.5 servers are in use — and treat those grants as root until a fix lands. For everyone else, the lesson is structural: the tools that make remote work convenient concentrate risk, and their flaws deserve the same urgency as flaws in the servers they protect. Watch for Tailscale's fixes and for a CVE or bulletin that gives these findings formal tracking. Readers' poll: should vendors be required to issue a fix or a bulletin before researchers publish flaws like these?
By The Numbers
FAQ
What is Tailscale SSH, in plain language?
Tailscale is a tool that connects a company's computers and servers into a private network over the internet, so they can talk to each other securely. Tailscale SSH is its feature for logging into those machines remotely. SSH, or Secure Shell, is the standard way administrators log into a server from elsewhere. The Tailworm findings concern what an attacker can do once Tailscale SSH and its port-forwarding option are switched on.
What does reaching 'root' mean?
Root is the highest level of control on a computer system — the administrator account that can read, change or delete anything, including security settings. An attacker who reaches root on a server effectively owns that server. That is why a chain that ends in root access is treated as severe even if it needs several steps to get there.
Is Tailscale a public company?
No. Tailscale is a private company, so it has no stock ticker of its own. Zscaler (ZS), a listed cybersecurity company, appears here only as a public read-through: a peer in the network-security industry whose business is affected by the same questions about remote-access security. ZS was not involved in the Tailworm findings.
Source: The Hacker News
AI Agent Update