Tailscale has released version 1.104.4 to address four groups of security flaws affecting its SSH and Serve features after researchers disclosed a broader set of weaknesses in the mesh VPN software and the self-hosted headscale control server. The company’s security bulletins describe problems that could let an authorized peer reach root-only Unix sockets, expose a node’s local API, exhaust memory in the Tailscale daemon or cause access-capability information to cross between services. Tailscale published the bulletins on October 26, and the patched client release followed on October 28.
The most serious SSH issue, tracked as TS-2026-014, involved Unix-socket forwarding. Tailscale’s SSH server runs inside the root-privileged tailscaled process and previously performed socket operations as root after checking the requested paths. A peer with an approved SSH connection and forwarding permission could potentially reach protected sockets such as Docker’s or Tailscale’s local API. Tailscale changed the implementation so Unix-socket forwarding is performed on behalf of the authenticated user rather than as root. A separate Serve issue, TS-2026-016, allowed TCP forwards to reach privileged Unix sockets, including the local API, which could give an attacker full control of an affected node under the configurations described by the company.
Two other bulletins cover service disruption and access-control handling. TS-2026-015 allowed an authenticated SSH peer to cause unbounded memory growth in tailscaled, potentially triggering an out-of-memory kill and interrupting the node’s Tailscale connections. TS-2026-017 involved a race condition in HTTP/2 Serve connections that could cause capability values intended for one service mount to be used with requests for another. Tailscale says this issue affects nodes with TLS-enabled Serve, at least two mounts with different capability requirements and concurrent streams on the same connection.
All four security bulletins identify Tailscale 1.104.4 or newer as the fixed version. The company’s release notes list the changes. Tailscale advises users of SSH with local or remote forwarding and Serve with Unix-socket backends to upgrade. As a temporary mitigation for SSH forwarding, administrators can set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled service environment and restart the service. The affected conditions require particular permissions or configurations; Tailscale does not describe these issues as unauthenticated attacks.
The wider Tailworm report from Cyberdione Labs described 11 findings across Tailscale client software, the experimental conn25 app connector and the self-hosted headscale control server. Tailscale’s four bulletins cover the SSH and Serve issues it addressed in version 1.104.4, but the company has not said that every finding in the broader research has been resolved. Administrators using headscale or experimental connector configurations should review the researcher’s technical report separately. The disclosure also adds to wider questions about how organizations configure and harden remote access VPNs.
If this article helped you, please consider supporting our work. Every small contribution keeps Abijita.com independent and running.
