Tailscale SSH Security Fixes: Version 1.104.4 and Official Advisories

The Tailworm research report describes lab testing conducted October 22–24, 2026, against Tailscale 1.104.2 and headscale 0.29.5. On October 28, Tailscale published its own investigation and announced fixes in Tailscale v1.104.4. Operators should now prioritize updating and reviewing their SSH access policies.

Image source: Tailscale (official SSH findings and fixes, October 28, 2026)

According to Tailscale's official findings and fixes, these vulnerabilities do not let unauthenticated internet attackers connect to arbitrary SSH servers. Exploitation requires prior access to an authorized tailnet peer and an SSH connection permitted by the existing tailnet policy.

Eleven Reported Findings and the Confirmed Impact

The testing evaluated Tailscale version 1.104.2 alongside headscale version 0.29.5, grouping the identified issues into five architectural functional areas.

The research covered SSH, Serve/Funnel, app connectors, relay behavior, and headscale. Not all eleven reported findings represent confirmed, unpatched exploitable vulnerabilities. Tailscale says some Serve/Funnel findings describe intended behavior; the reported Conn25 app connector issue affected an unreleased pre-production feature, not stable connectors. Headscale server findings belong to a separate project and require their own remediation assessment; updating the Tailscale client to 1.104.4 does not establish that they are fixed.

• Daemon Execution Context: The Tailscale SSH server operates directly inside tailscaled, the background daemon that runs with full root privileges on the host machine.
• Privilege Boundary Error: An authorized SSH connection could use Unix socket forwarding with elevated privileges beyond those of the connected user. In v1.104.4, Tailscale performs this forwarding under the authenticated user's permissions.

Version 1.104.4 Fixes and Operator Actions

The researchers described issues in controlled test environments. The published vendor material does not establish whether exploitation has occurred in the wild.

Exploitation of the SSH findings requires prior access to an authorized tailnet peer and an SSH connection permitted by the tailnet policy. These are not unauthenticated direct external exploits of arbitrary hosts.

Tailscale lists the SSH forwarding and session memory fixes in its changelog, with corresponding disclosures in security bulletins TS-2026-014 through TS-2026-017. Operators should take these steps:

• Install the Fixed Release: Upgrade systems running Tailscale SSH or affected Serve functions to Tailscale v1.104.4 or later.
• Disable Unused SSH Endpoints: Where native Tailscale SSH is unnecessary, reduce exposure with tailscale set --ssh=false.
• Audit Access Control Lists (ACLs): Review tailnet SSH policies to eliminate overly permissive configurations, specifically auditing for unconstrained users: ["root"] directives and wide-open autogroup:nonroot assignments.

Sources

• Tailscale: SSH Findings and Fixes, October 28, 2026
• Tailscale: Changelog for v1.104.4
• Tailscale: Security Bulletins TS-2026-014 to TS-2026-017
• Cyberdione Labs: Original Tailworm Research