The short version
- The flaws. Cyberdione Labs reported 11 issues in Tailscale 1.104.2 and the self-hosted headscale 0.29.5 control server, tested in a lab on released software. The most serious is in Tailscale SSH, whose server component runs with root privileges.
- What an attacker needs. A device must already be permitted by the network's access rules to open an SSH session to the target, with forwarding allowed in that rule. No password or key is required, because Tailscale SSH trusts device identity and policy.
- The fix. Version 1.104.4 changes forwarding to run as the logged-in user rather than as root and covers four security bulletins. headscale 0.29.5, released on 13 October, does not fix the reported issues and cannot turn forwarding off.
- The worm dispute. Windisch called the chain wormable, with one compromised device spreading to every device the policy allows in under a second per step. Tailscale rejected the term, describing lateral movement limited to connections the policy already permits.
- Not seen in the wild. Neither Tailscale nor the report says the flaws have been used in real attacks, and the proof-of-concept code is not public.
Timeline
| Date | Event |
|---|---|
| June | Tailscale fixes a separate flaw in Tailscale SSH's Unix socket forwarding, which let an unprivileged user reach a privileged socket, in version 1.98.9. |
| 13 Oct | headscale version 0.29.5 is released; it does not fix the issues later reported. |
| 24 Oct | Tailscale says it received Cyberdione Labs' report on the morning of Saturday 24 October, about two hours before it was published. |
| 25 Oct | The Tailworm report by Erica Windisch is published, according to The Hacker News. |
| 27 Oct | Tailscale says it is working on patches and aims to ship a fix by the end of the day. |
| 28 Oct | Tailscale releases version 1.104.4 covering four security bulletins. |
How the flaws work
Tailscale SSH does not check a password or key. It identifies the connecting device, and the network's policy file decides whether that device may open a session to a target. The background process that forwards connections inside an approved session runs as root. Cyberdione Labs found that a forwarded connection to a Unix socket — a local endpoint programs on the same machine use to talk to each other — was checked as a path and then handled as root, and that a timing trick could swap the path after the check. Forwarding to the Docker control socket gave a root shell in testing.
The attacker still needs a starting point on one device. The report lists the usual routes: a vulnerable web application, a poisoned software package, phishing, or stolen login details. Tailscale does not create that first foothold, and according to the company a permitted session can reach only the machines the policy already allows.
Other findings and who is exposed
The report covers app connectors, the serve feature, the DERP relay used between devices, and headscale. Its app connector finding is in conn25, an experimental feature. Tailscale says conn25 has not been released and that the connectors customers use today are not affected. Of five serve and funnel findings, Tailscale says it fixed three and considers the other two to work as designed.
Tailscale SSH's server runs only on Linux and the open-source macOS build; the attacker's own device can be any platform. In 1.104.4 Tailscale moved forwarding to the logged-in user and now relies on the operating system's file permissions instead of its own path check. The bulletins carry no CVE identifiers or severity scores and none states the oldest affected version.
Self-hosted deployments are in a worse position. On headscale, forwarding is granted on every accepted session and cannot be switched off in the policy, so Windisch's report says every SSH grant there should be treated as giving root on the target.
Worm claim and disclosure
Windisch measured a single compromised device spreading to every device the access rules allowed, without passwords, stolen keys or user action. Two controls stopped it in her tests: rules written as single device-to-device pairs, and device keys bound to hardware such as a TPM or Secure Enclave. Tailscale said the findings do not describe self-replicating malware. It called the privilege-escalation problems serious: "These are serious security issues, and we're treating them accordingly."
Windisch has described the release as reported but not coordinated, and later said she sent the report and proof-of-concept code to Tailscale's security contact beforehand. Tailscale says engineers were already examining the same code and that it has reproduced the main findings. The sources differ on the publication date: The Hacker News gives 25 October, while Tailscale's account of receiving the report about two hours before publication puts it on 24 October. Other researchers have questioned the worm description.
What is not known yet
- Which exact Tailscale and headscale configurations are affected; Tailscale said it was still working out the scope.
- Whether the flaws have been used against any real network.
- How old the affected Tailscale releases are, since the bulletins do not say.
- Whether headscale will gain a way to disable SSH forwarding.
- Whether any enrolment key captured in an attack has been used to add a device to a network.
What to do
If you run Tailscale SSH
- Update to version 1.104.4 or later; where a server cannot be updated yet, set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled service environment and restart the service.
- Rewrite access rules as single source-to-destination pairs naming one device and one target, and remove broad grants made by identity or tag.
- If a device may be compromised, delete it at the control plane, because reimaging does not revoke a key an attacker may have copied.
- Do not rely on SSH check mode for these flaws; it adds a sign-in step at the start of a session but does not stop forwarding inside an approved one.
If you run headscale
- Treat every SSH grant as giving root on the target, since forwarding cannot be turned off on headscale 0.29.5.
- Tighten SSH access policies so only the specific users and devices that need access can connect.
For everyone else
- Turn on node-key expiry and bind device keys to hardware such as a TPM, so a stolen device identity cannot be reused elsewhere.
- Remove app connector permissions and any tailscale serve forward pointing at a Unix socket from devices that do not need them.
- Enable automatic updates so client fixes are applied without waiting for a maintenance window.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.