Tailscale SSH security now has a fix. After an October 26 investigation notice, Tailscale released v1.104.4 and published four security bulletins, TS-2026-014 through TS-2026-017, covering the confirmed vulnerabilities. In its blog post “Tailscale SSH: Findings and fixes,” the company says: “If you use Tailscale SSH, we recommend updating to this release or later.”
What Tailscale found
Tailscale says the SSH issues involved how permissions were enforced after a connection was authorized. In some cases, an authenticated SSH session could act beyond its configured local user’s privileges, including through SSH forwarding. The findings trace to a report called “Tailworm” from an unnamed external security researcher. The report also described five findings in Tailscale Serve and Funnel. Tailscale says it fixed three and that the other two work as designed. It also identified a vulnerability in Conn25, an unreleased app connector, and says “The stable app connectors available today are not affected.”
How serious the Tailscale SSH security risk is
Tailscale’s framing is narrow. “Exploitation requires an existing foothold on an authorized peer in the tailnet,” the post says, and the vulnerabilities “don’t allow an unauthenticated attacker to connect to arbitrary Tailscale SSH servers.” The exposure is greatest where many people or devices can reach sensitive machines. Neither the blog post nor the investigation page gives a severity rating or CVE identifiers, and neither says whether exploitation has been seen in the wild. The TS-2026 numbers are Tailscale’s own bulletin IDs, not CVEs.
What admins can do now
Tailscale’s guidance is to update to v1.104.4 or later, review Tailscale SSH policies so access reaches only the users and devices that need it, and consider SSH check mode for sensitive systems, which adds an extra authentication check before access is granted. Before the patch, the company’s October 26 update described a stopgap: setting TS_SSH_DISABLE_FORWARDING=1 in the environment of the tailscaled service, which it said mitigated several of the more serious findings.
What is still unclear
The investigation page, updated October 27, still describes a release as pending in its remediation section, while the blog post names the fixed version, so admins should confirm the exact release in Tailscale’s changelog. When we checked, the public bulletin index still listed TS-2026-013 as the newest entry. Until the four bulletins are readable there, the details on affected functionality and exploitation conditions rest on Tailscale’s blog post alone.
It lands in a busy stretch for admins. Recent weeks have brought the GitLab flaw rated a perfect 10 and the chained Ivanti zero-days on Connect Secure. In those cases the vendors published versions and scores. For Tailscale SSH security, the useful steps are the update and an access review.
