Tailworm: what Tailscale’s four security advisories confirm

 Conceptual illustration of a privilege-boundary flaw; it does not depict a real Tailscale system or exploit. Tailscale published its account of the “Tailworm” disclosure on October 28, confirming four security issues in Tailscale SSH and Serve. The vendor says all four are fixed in Tailscale 1.104.4 or later. These advisories use Tailscale bulletin IDs TS-2026-014 through TS-2026-017; they do not list CVE identifiers. The most serious issue, TS-2026-014, involved Unix-socket forwarding in Tailscale SSH. The root-privileged `tailscaled` process checked socket paths but performed forwarding operations as root. Local (`-L`) or remote (`-R`) forwarding, combined with a path-replacement race, could let an already-authorized peer reach root-only sockets such as Docker’s or Tailscale’s local API. In practice, that could cross the privilege boundary and compromise the target node. It was not an unauthenticated internet entry point: an attacker first needed a foothold on an approved tailnet device, SSH access permitted by policy, and forwarding enabled. The other bulletins cover memory exhaustion in an authenticated Tailscale SSH session (TS-2026-015), `tailscale serve` exposing privileged Unix sockets through backend forwarding or a symlink race (TS-2026-016), and an HTTP/2 race that could mix capability headers between Serve mounts (TS-2026-017). Tailscale says the “worm” label does not mean self-replicating malware; movement was limited to connections already allowed by tailnet policy. The researcher’s broader report contains 11 findings across Tailscale, headscale and experimental features. Tailscale’s four bulletins are the confirmed issues it says it fixed; the vendor says Conn25 is pre-release and stable app connectors are unaffected. Updating Tailscale does not patch separate headscale findings. If you use Tailscale SSH or Serve, upgrade to 1.104.4 or newer and review who can SSH to which nodes. If an immediate upgrade is not possible, Tailscale documents disabling SSH forwarding with `TS_SSH_DISABLE_FORWARDING=1` and restarting `tailscaled`; that mitigates the forwarding issue, not every Serve finding. [Tailscale’s explanation](https://tailscale.com/blog/tailscale-ssh-findings-fixes), [its four bulletins](https://tailscale.com/security-bulletins) and [the researcher’s report](https://www.tailworm.com/) detail the conditions and fixes. ~cybersecurity