Act nowVulnerabilities

Tailscale fixes SSH flaws that could reach root-only sockets: update to 1.104.4 if you use Tailscale SSH

On 26 Oct 2026 Tailscale published four bulletins, TS-2026-014 to TS-2026-017, all fixed in 1.104.4. The most important one lets a permitted SSH peer reach root-only sockets such as Docker's. Here is who must act.

Updated 29 Oct 2026: see what changed

How urgent

Act now

Who is affected

Anyone running Tailscale on a server before version 1.104.4, mainly where Tailscale SSH is on and the access policy allows port or socket forwarding. Other bulletins affect Tailscale Serve and SSH session memory

What to do

Update Tailscale to 1.104.4 or newer on every server. If you cannot update today, set TS_SSH_DISABLE_FORWARDING=1 for the tailscaled service and restart it, and check which people your policy lets forward

Published 28 Oct 2026 · Sources last checked 29 Oct 2026No. 17 / 87

Updates, follow-ups and corrections

  1. Update · 29 Oct 2026. Tailscale has now answered the researcher report. The report is called Tailworm and was published over the weekend of 24-25 Oct by Cyberdione Labs; press says it lists 11 findings and claims the SSH flaws could spread like a worm. In its own statement of 28 Oct, Tailscale says version 1.104.4 fixes the confirmed findings, which are the four bulletins we cover (it also says two Serve and Funnel points work as designed and that its stable app connectors are not affected). Tailscale says an attacker needs a foothold on an authorized device and an SSH permission in your policy, that unauthenticated attackers cannot connect to arbitrary Tailscale SSH servers, and that this is lateral movement limited by your policy, not a self-replicating worm. It reports no attacks in the wild. We read Tailscale's statement and the press coverage, not the Tailworm report itself. Beyond updating to 1.104.4, Tailscale advises limiting SSH access to the users and devices that need it and considering SSH check mode for sensitive servers.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On 26 October 2026 Tailscale published four security bulletins. All four are fixed in version 1.104.4 or newer.

The one that matters most for small teams is TS-2026-014. Tailscale SSH let a person connect to a server over Tailscale without managing SSH keys. When the access policy also allowed forwarding (ssh -L or ssh -R), the server could be tricked into connecting as root to sockets that only root should reach. A socket is a local door between programs. Two examples Tailscale gives are the Docker socket and the local control interface of Tailscale itself. Tailscale says the list of allowed paths stopped being a real security boundary.

The other three are narrower:

  • TS-2026-015: a person already allowed to open an SSH session could use up the server's memory, which could stop Tailscale on that machine and cut its connections.
  • TS-2026-016: Tailscale Serve with Unix socket backends could reach root-only sockets when a local user could change the Serve setup or the backend paths.
  • TS-2026-017: with Serve over TLS, two mounts with different permissions on one machine could, in a race, hand out the wrong permission values.

Who is affected

People who run Tailscale on their own servers and use Tailscale SSH, or Tailscale Serve, on a version before 1.104.4. For TS-2026-014 the problem needs Tailscale SSH on and a policy that allows forwarding. The attacker must already be a permitted peer on your network, so this is a risk from inside your tailnet, not from the open internet. If you only use Tailscale as a normal VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary on a laptop, this is much less likely to affect you.

Is it being attacked?

None of the four bulletins mentions attacks in the wild, and we have not found a confirmed report of any. Some press coverage describes a researcher report with further claims. We could not open that report, so we rely only on Tailscale's own bulletins here.

Why it matters if you build with AI

Small teams and AI-assisted projects often reach a cloud server or a build machine over Tailscale SSH, and the same machine often runs Docker. Reaching the Docker socket as root is close to owning the server, and with it every key and environment variable stored there. It is the same kind of damage as in the GitLab and Railway stories this month, but through a door you opened yourself.

What to do

  1. Update Tailscale to 1.104.4 or newer on every server. Check the version with tailscale version. Tailscale lists no other fix.
  2. If you cannot update today, turn off forwarding. Set TS_SSH_DISABLE_FORWARDING=1 in the environment of the tailscaled service and restart it. Tailscale says this switches off forwarding without switching off the rest of Tailscale SSH.
  3. Review who your policy lets forward. Allow forwarding only to the people and machines that need it. This is our advice, not Tailscale's.
  4. Treat access to a server as strong access. Anyone who can log in over Tailscale SSH, including through a shared build machine, deserves the same care as a person with a key. This is also our advice.
  5. After updating, look at your logs. Check for forwarded connections or sessions you do not recognise. If you find any, rotate the keys and tokens stored on that server.

What we could not confirm

We read Tailscale's bulletins for TS-2026-014, 015, 016 and 017, but not the last part of the page, and we have not tested the flaws or the fix. The bulletins do not name who reported the flaws or say how many people are affected. They do not mention attacks, and that can change. For exact upgrade steps, use Tailscale's documentation.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks