Unpatched Tailscale SSH flaws can turn one compromised device into root access across a network (TAILWORM)

25 October 2026High

Tailscale · Tailscale SSH and headscale · TAILWORM

Unpatched Tailscale SSH flaws can turn one compromised device into root access across a network

A researcher's report, Tailworm, describes eleven findings in Tailscale and the self-hosted headscale server. The most serious: where Tailscale SSH allows port forwarding, an attacker who already controls one device can reach root-only sockets on other machines and run commands as root, then move from device to device. In lab tests it also captured an enrolment key and joined a rogue device to networks without Tailnet Lock. There is no CVE or fixed version yet and no attacks have been reported. Tailscale says it is working on fixes, but is not advising everyone to turn off Tailscale SSH.

Affected: Tailscale SSH where rules allow port forwarding (tested on Tailscale 1.104.2), and headscale 0.29.5, where forwarding cannot be turned off. Other findings cover app connectors (including the experimental conn25), tailscale serve and headscale. Tailscale is still working out which setups are affected.
What to do: There is no patch yet. Write Tailscale SSH rules as single device-to-device pairs rather than broad user or tag grants, and turn off port forwarding in those rules where you can; on headscale, treat every SSH grant as root on the target. Remove app connector permissions that aren't needed and any tailscale serve forward to a Unix socket. Turn on node-key expiry. If a device is compromised, delete it in the admin console, as reimaging alone doesn't revoke its keys. Update as soon as Tailscale ships fixes.General information summarised from the vendor's advisory at the time of writing, not professional advice. Check the vendor's current advisory before acting.
Why it’s here: Tailscale is widely used for remote access to office and client servers. The report is public, there is no fix yet, and the vendor has confirmed it is working on the issues.

Unpatched Tailscale SSH flaws can turn one compromised device into root access across a network

Affected

Tailscale SSH where rules allow port forwarding (tested on Tailscale 1.104.2), and headscale 0.29.5, where forwarding cannot be turned off. Other findings cover app connectors (including the experimental conn25), tailscale serve and headscale. Tailscale is still working out which setups are affected.

What to do

There is no patch yet. Write Tailscale SSH rules as single device-to-device pairs rather than broad user or tag grants, and turn off port forwarding in those rules where you can; on headscale, treat every SSH grant as root on the target. Remove app connector permissions that aren't needed and any tailscale serve forward to a Unix socket. Turn on node-key expiry. If a device is compromised, delete it in the admin console, as reimaging alone doesn't revoke its keys. Update as soon as Tailscale ships fixes.General information summarised from the vendor's advisory at the time of writing, not professional advice. Check the vendor's current advisory before acting.

Why it’s here

Tailscale is widely used for remote access to office and client servers. The report is public, there is no fix yet, and the vendor has confirmed it is working on the issues.