Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

A Researcher Published 11 Tailscale SSH Flaws, Now Fixed in v1.104.4: How to Contain Your Mesh VPN When One Device Gets Popped

Two IT engineers discussing network containment in a server room aisle

Written by

in

Mesh VPNs sold us on “every device is its own perimeter.” That only holds if one bad laptop cannot walk straight to root on the database box. This week’s Tailscale SSH vulnerability root access disclosure says the ACL you trusted may not be the wall you thought it was, at least for Tailscale SSH with forwarding enabled.

What the Researcher Published

On October 24–25, 2026, Erica Windisch of Cyberdione Labs published Tailworm, a lab security assessment of Tailscale client v1.104.2 and self-hosted headscale v0.29.5. The report lists 11 findings across Tailscale SSH, experimental conn25 app connectors, serve/funnel, the DERP client, and headscale. All were “verified by reproduction in a lab environment on unmodified, released software,” the report says. It describes lab tests, not attacks seen on customer networks.

The headline class is Tailscale SSH unix-socket forwarding (findings 1–3). Per the report, forwarding path checks and file operations run as root inside tailscaled. With one approved device and an SSH policy rule that permits forwarding, an ordinary session can dial or replace privileged sockets such as Docker or systemd. Windisch reports lab results of root execution on targets, capture of enrollment keys, and, on a Tailnet-Lock-disabled lab setup, joining a rogue node. The report’s own words: restricting SSH to non-privileged accounts is “defense-in-depth only” and “does not mitigate these findings.” Check mode, it says, gates session start only and does not constrain forwarding once a session is open.

Other findings cover experimental app connectors choosing destinations outside ACL visibility, a serve TCP forward to the local admin API, memory exhaustion in SSH sessions and relays, and headscale onboarding lockout. Those are researcher claims with lab evidence; treat them as Cyberdione Labs data until Tailscale publishes its own per-finding advisory.

Patch Status: Fixed in Tailscale v1.104.4

Update, November 3, 2026: Tailscale has shipped a fixed client. Tailscale v1.104.4, released October 28, 2026, makes Tailscale SSH perform Unix socket forwarding as the authenticated user rather than as root, which blocks peers from reaching root-only sockets such as the Docker socket or the tailscaled local API. The same release bounds SSH session memory and tightens serve Unix backends. Tailscale published these as security bulletins TS-2026-014 (SSH Unix socket forwarding to root-only sockets), TS-2026-015 (SSH session memory exhaustion), TS-2026-016 (serve Unix backends reaching privileged sockets), and TS-2026-017 (HTTP/2 serve capability mix-up), each fixed in “1.104.4 or newer.” v1.104.3 was internal-only, and the current client is v1.104.5 (November 2). If you use Tailscale SSH or Serve, upgrade to v1.104.4 or newer now.

For the record, this post was first drafted on October 27, when the newest public client was still v1.104.2, the version the researcher tested. On October 26, Tailscale published Tailscale SSH: Investigation and remediation update, calling the privilege-escalation issues “serious security issues” and targeting a release by the end of October 27. The fixed build landed a day later.

On notice timing: The Hacker News reports Windisch saying she sent the report and proof-of-concept to Tailscale’s security contact on the Saturday before the public post, and she described the process on Hacker News as “reported but not coordinated.” The Tailworm write-up itself argues for “rapid awareness” to speed remediation. Treat notice timing as disputed enough that “without warning” overstates it.

What Tailscale Confirms Versus What Remains Researcher-Only

Tailscale confirms a serious privilege-escalation class for authorized SSH sessions and says exploitation “depends on the permissions granted to the connecting user or device, the system’s configuration, and other conditions.” It is “not recommending that everyone disable Tailscale SSH.” Its bulletins cover the SSH forwarding, SSH memory, and serve findings with a fixed version, but it has not published a finding-by-finding confirmation of all 11 Tailworm items. Separately, do not confuse this week with earlier 2026 bulletins TS-2026-006 and TS-2026-009, which fixed different Tailscale SSH tricks that could reach root despite autogroup:nonroot and were patched in v1.98.9. Tailworm’s core claim is a different class: forwarding that runs with daemon privilege from an already-allowed unprivileged session.

My Recommendations: Contain the Mesh Now

The steps below mix Tailscale’s published interim advice with my own operator opinion. This is not a substitute for Tailscale Support.

  1. Disable SSH forwarding where you do not need it. Tailscale’s update says to set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled environment and restart. That mitigates several of the more serious findings without turning SSH off. On SaaS, also deny forwarding per SSH rule. On headscale 0.29.5, the researcher says forwarding cannot be disabled per rule, so treat every SSH grant as high risk until you can upgrade.
  2. Rewrite SSH rules as per-pair grants. Specific source device to specific destination. Drop identity-wide and tag-wide accept rules. The report calls per-pair grants the control that stopped lab spread.
  3. Audit serve and app connectors. Remove serve TCP forwards to unix sockets, especially anything aimed at tailscaled.sock. Pull connector entitlements from devices that do not need them.
  4. Upgrade to v1.104.4 or newer and plan containment. Update every node and turn on auto-updates where you can. If a device is compromised, delete it at the control plane. Reimaging alone does not revoke keys an attacker may have copied off the host. That last point is the researcher’s claim; Tailscale’s update does not repeat it, but it is sound incident practice in my view.

Picture this hypothetical. A developer laptop is phished. That laptop already has a Tailscale SSH rule to your CI hosts with forwarding left on. Under the researcher’s model, that foothold is the whole prerequisite. Tighten the rule and kill forwarding before you need the hypothetical to become a ticket. That scenario is my illustration, not a reported breach.

The Bottom Line

Eleven lab-verified findings are public. Tailscale agrees the SSH privilege-escalation class is serious and shipped fixes in v1.104.4 on October 28, 2026. Until every node runs v1.104.4 or newer, assume Tailscale SSH with forwarding is a lateral-movement path from any device your policy already trusts, and shrink that trust now.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *