Skip to content
Home Tutorials Roadmaps Courses Classroom Training Blog
Log in Join free

Tailworm: Tailscale SSH Flaws Patched After Early Disclosure, Lessons for Developers

Researchers disclosed 11 Tailscale flaws called Tailworm on 25 October 2026. What happened, the fix, and what learners should do.

SA SukhNexus Academy 5 min read
Tailworm: Tailscale SSH Flaws Patched After Early Disclosure, Lessons for Developers

Many students and young developers use Tailscale to reach a home server, a Raspberry Pi or a cloud machine without opening ports to the internet. Last week, a security report called Tailworm showed serious flaws in one of its features, Tailscale SSH. Tailscale has since released fixes for most of the problems. Here is what happened, and what you can learn from it.

What happened

On 25 October 2026, researcher Erica Windisch of Cyberdione Labs published the Tailworm report. It lists 11 findings affecting version 1.104.2 of the Tailscale client and version 0.29.5 of headscale, an open-source control server that organisations can run themselves instead of using Tailscale's hosted service.

According to SecurityWeek, six of the findings are rated high severity, and four of those concern Tailscale SSH. This feature lets you log in to machines based on device identity and network rules, instead of passwords or keys.

The main problem: Tailscale SSH does some forwarding work with root (administrator) privileges, and the report says the safeguards around it can be bypassed. So an attacker who has already hacked one device could gain root access on other servers that device is allowed to reach over Tailscale SSH, if the access rule allows forwarding. The full attack chain worked only on networks where Tailscale's Tailnet Lock feature was not turned on, The Hacker News reported.

The researcher called the result "wormable", meaning it could spread from machine to machine automatically. This label is disputed: some researchers who read the report publicly questioned it, while others called the root-access finding serious. Also note that this is not an attack that works against every Tailscale user from the outside. The attacker first needs control of a device inside the network.

The disclosure itself caused debate. The report was published before any patch existed. At that time there was no security bulletin, no CVE number and no fixed version. The researchers argued that quick public awareness would speed up fixes, but others criticised the move on social media. The proof-of-concept code was not made public and was shared only with Tailscale.

How Tailscale responded

Tailscale's vice president of engineering, Mike Shaver, replied on Reddit that the company had received the report and was already looking at the same areas. On 27 October, Tailscale said on its website that it had published four security bulletins, had implemented fixes for most of the issues, and was testing a patched release.

Security firm Brandefense, which is tracking the case, reports that the four bulletins (TS-2026-014 to TS-2026-017) name version 1.104.4 as the fixed version, and that this version appeared on GitHub on 28 October. As of 28 October, Brandefense said a few items, including part of one headscale finding, were still open. Check Tailscale's own bulletins page for the latest status, because things may have changed since then.

Why it matters for learners and developers in India

Tools like Tailscale are popular with developers for home labs, side projects and small teams. They feel safe because they are "private". Tailworm is a reminder that a private network is only as safe as its weakest device. If one laptop is infected, every server it is allowed to reach is at risk.

This story also teaches real-world security ideas that interviewers for DevOps, cloud and security jobs like to ask about:

  • Lateral movement: an attacker moving from one hacked machine to others.
  • Least privilege: give each device and user only the access it truly needs.
  • Running code as root: any bug in code with full privileges becomes far more dangerous.
  • Responsible disclosure: the debate about publishing flaws before a fix is ready.

What to do next

If you use Tailscale

  1. Update now. Check your installed version (the tailscale version command shows it) and move to 1.104.4 or newer on every device.
  2. Review your access rules. Remove broad rules such as "every device can SSH to every server". Allow forwarding only where you really need it.
  3. Turn off Tailscale SSH if you do not use it. Tailscale documents the command tailscale set --ssh=false. Before you run it on a remote machine, make sure you have another way to log in, or you may lock yourself out.
  4. Read the official bulletins. They explain which setups are affected and what to change. Bulletin TS-2026-014 also documents a TS_SSH_DISABLE_FORWARDING=1 setting for forwarding.
  5. Consider Tailnet Lock for networks that matter, since the full attack chain did not work where it was enabled.

If you are still learning

Use this news as a study topic. Learn how SSH works, what port forwarding is, what Unix sockets are, and why the root user is special on Linux. Our free Computer Science tutorial is a good place to build these basics.

Practise reading a real security bulletin from start to end. Note the affected versions, the fixed version and the suggested workarounds. This habit will help you in any job where you manage servers.

If security, cloud or DevOps interests you as a career, look at our career roadmaps to plan the skills you need step by step.

Simple rule: update your tools quickly, give every device the least access it needs, and switch off features you do not use.
SA

Written by

SukhNexus Academy

SukhNexus IT Solutions, Bathinda

Reading is step one

Now learn it hands-on

Practise for free in the browser, take a full online course, or join a classroom batch in Bathinda.