> ## Content Index
> Fetch the complete content index at: https://blog.harshkohli.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Tailscale Confirms SSH Flaws, Patch Due Within a Day
- URL: https://blog.harshkohli.com/tailscale-confirms-ssh-flaws-patch/
- Published: 2026-10-27T07:02:28.000Z
- Updated: 2026-10-27T07:02:28.000Z
- Description: Tailscale calls the Tailworm SSH issues serious privilege escalation bugs and is targeting a fix by Oct 27. Here is what to change on your tailnet now.
- Author: Harsh Kohli
- Tags: Tech News, Software

Two days ago I wrote about the Tailworm report and the unpatched holes it claimed in Tailscale SSH. Back then the company had only replied on Reddit. Now Tailscale has put out its own investigation page, and it doesn't play the issue down. If you use Tailscale SSH on a home lab or at work, keep reading.

## What happened

Tailscale published a page called ["Tailscale SSH: Investigation and remediation update"](https://tailscale.com/ssh-investigation-update?ref=blog.harshkohli.com). It says most of the problems it has confirmed are privilege escalation. Put simply, someone who's already allowed to connect over Tailscale SSH may be able to do more than the local account they land in should allow, and in some cases that could mean higher privileges. Tailscale's own words are that these are "serious security issues."

It says fixes for most of the issues are built and in testing. The plan is a patched client by the end of Tuesday, October 27, as long as testing goes well. A full security advisory with affected versions comes after that, followed by a technical write-up. The researchers behind the [Tailworm report](https://tailworm.com/?ref=blog.harshkohli.com) have updated their page too. They list the fixes already merged into Tailscale's public code, including a rework of SSH forwarding so forwarded sockets run with the logged-in user's permissions instead of root's. None of that is in a numbered release yet, so version 1.104.2 and older are still exposed. [The Hacker News on X](https://x.com/TheHackersNews/status/2114961487999750239?ref=blog.harshkohli.com) was where I first spotted the confirmation.

## Why it matters

This isn't a case where any random person on the internet can walk into your machines. Tailscale itself points out that the attacker has to be someone already allowed in. What makes it scary is that one compromised laptop with broad SSH rules could hop to every server those rules allow. The original report showed that spread happening in a lab in under a second per hop. If your rules say "any of my devices can SSH into any of my servers," then one hacked device is effectively a key to all of them.

I also like that Tailscale isn't telling everyone to switch SSH off. It's a measured response, and it's still a real bug.

## What to do

- Install the patched client as soon as it ships. If auto-update is off on your servers, turn it on or check back tomorrow.
- Until then, if you don't use SSH forwarding, set `TS_SSH_DISABLE_FORWARDING=1` in the `tailscaled` service environment and restart it. Tailscale says this mitigates several of the worst findings.
- Narrow your SSH access rules so each source device can only reach the specific machines it actually needs.
- If you run headscale, treat every SSH grant as root-level for now, because forwarding can't be turned off there.

For background, my [first post on the Tailworm flaws](https://blog.harshkohli.com/tailscale-ssh-tailworm-unpatched-flaws/) covers the original findings, and [Tailscale vs WireGuard](https://blog.harshkohli.com/tailscale-vs-wireguard/) is worth a read if this has you rethinking your setup.