Tailscale Rushes Patches After Uncoordinated Disclosure of ‘Tailworm’ Flaws

What it is

Tailworm is a Cyberdione Labs report of 11 findings in Tailscale client 1.104.2 and headscale 0.29.5 (the self-hosted control server). Six are rated high severity. Cyberdione published before patches existed, and the page notes the criticism of that on social media. The researchers argued that fast awareness speeds remediation.

How it works

Tailscale SSH does some forwarding operations as root, and the safeguards meant to restrict them can be bypassed. An attacker with one compromised device can use this against any server that device may reach over Tailscale SSH, provided the access rule allows forwarding. In lab tests this gave root on target servers and let the attacker steal keys that can add rogue devices to the tailnet.

The foothold could come from phishing, a vulnerable web application or a malicious package. Because no user credentials are involved, an automated chain moved across every server the policy granted SSH access to, with no user interaction.

The remaining findings cover the experimental app connector feature, the Serve feature, headscale and the client's relay component. The report says these could reach cloud metadata services and internal networks while bypassing access rules, expose a node's administrative interface to remote peers, or cause denial of service. The page gives no further detail on these.

Preconditions / Affected

• Tailscale client 1.104.2 and headscale 0.29.5.
• For the SSH chain: an already compromised device, plus an access rule that permits SSH forwarding to the target.
• Tailscale VP of Engineering Mike Shaver said most issues concern what happens after someone is authorized to connect, and are not the same as an unauthenticated attacker reaching arbitrary machines. Impact depends on how SSH access is configured.

What to do

• Review Tailscale SSH access policies.
• Disable SSH forwarding wherever it is not needed. Tailscale says this mitigates several of the more serious findings.
• Watch for the patched client. Tailscale aimed to release it by the end of Tuesday, October 27, pending testing, with a security advisory and technical write-up to follow. The page does not confirm it has shipped.
• If you run headscale or use app connector, Serve or relay features, the page offers no specific mitigation. Check the advisory once published.

Caveats

• Tailscale says it is not recommending that everyone disable Tailscale SSH.
• Fixes for several findings are in Tailscale's public repositories but had not reached a numbered release when the report was last updated on Tuesday.
• Neither Tailscale nor the report mentions exploitation in the wild.
• The speed and wormable results come from lab tests by the researchers, not independent reproduction.