分级SSH：调查和补救更新
2026年10月26日发布。
我们正在调查影响Tailscale SSH的安全漏洞，并想分享我们发现的，我们在做什么，客户应该知道的。
我们的工程和安全小组在外部安全专家的帮助下一直在调查所报告的问题。 这基于已经开始的工作，我们已经加速了处理结果和准备解决。
我们找到的
我们发现的大部分标本SSH问题都涉及特权升级在某些情况下，已经授权在 Tailscale SSH 上连接的人可能能够执行超出其配置的本地用户权限的行动，包括可能获得更高的权限。
这些是严重的安全问题，我们正在相应处理。
开发取决于给予连接用户或设备的权限，系统的配置，以及其他条件。 我们正在继续核实发现的全部范围以及哪些配置可能会受到影响
根据目前的评估，我们不建议每个人禁用Tailscale SSH。
补救进展
我们的工程师已经对已查明的大多数问题进行了修正，并正在完成测试，以提前发布补丁客户端。
我们的目标是在10月27日星期二结束前发布前提是测试成功完成当补丁版本可用时，或者如果时间线发生变化，我们将更新这个页面。
我们正在继续审查剩下的调查结果，并核实我们的变化是否解决了根本问题。
客户现在能做的
当我们准备更新时，我们建议审查你的尾巴SH配置：
- 审查SSH接入政策。 确保接入仅限于需要的用户和设备。
- 不需要就禁用SSH转发设置 TSH DISH FORWARDING=1 在尾部缩放的服务环境中重新启动服务。 这样可以使SSH转发不完全损坏Tailscale SSH，并减轻一些更严重的发现。
- 审查进入敏感系统的机会。 在我们调查时考虑暂时收紧您的 Tailscale SSH 访问政策，这样只有需要访问的特定用户和设备才能连接。
- 准备更新。 可用时应用补丁的 Tailscale 客户端释放。
接下来会发生什么
一旦修复完成，我们将发布一个安全咨询，详细列出已确认的弱点，受影响的版本和配置，其影响，以及如何解决这些问题。 如果有这方面的信息，我们将与之联系起来。
以及我们所做的工程改变
如果我们的评估改变或者我们确定任何额外的步骤客户需要采取，我们将传达这些。
如果您对您的特定环境有疑问，请联系Tailscale Support。
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
Tailscale SSH: Investigation and remediation update
Published October 26th 2026.
We're investigating security vulnerabilities affecting Tailscale SSH and wanted to share an update on what we've found, what we're doing about it, and what customers should know.
Our engineering and security teams have been investigating the reported issues with help from external security specialists. This builds on work already underway, which we've accelerated to address the findings and prepare fixes.
What we've found
Most of the Tailscale SSH issues we've identified concern privilege escalation. In some circumstances, someone already authorized to connect over Tailscale SSH may be able to perform actions beyond the permissions of their configured local user, including potentially gaining elevated privileges.
These are serious security issues, and we're treating them accordingly.
Exploitation depends on the permissions granted to the connecting user or device, the system's configuration, and other conditions. We're continuing to verify the full scope of the findings and which configurations may be affected.
Based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
Remediation progress
Our engineers have implemented fixes for most of the issues identified and are completing testing ahead of a patched client release.
We're targeting a release by the end of Tuesday 27 October, subject to successful completion of testing. We'll update this page when the patched version is available, or if that timeline changes.
We're continuing to review the remaining findings and verify that our changes address the underlying problems.
What customers can do now
While we're preparing the update, we recommend reviewing your Tailscale SSH configuration:
- Review SSH access policies. Make sure access is limited to the users and devices that need it.
- Disable SSH forwarding if you don't need it. Set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled service environment and restart the service. This disables SSH forwarding without disabling Tailscale SSH entirely, and mitigates several of the more serious findings.
- Review access to sensitive systems. Consider temporarily tightening your Tailscale SSH access policies while we investigate, so that only the specific users and devices that need access can connect.
- Prepare to update. Apply the patched Tailscale client release when it becomes available.
What happens next
Once the fixes are available, we'll publish a security advisory detailing the confirmed vulnerabilities, affected versions and configurations, their impact, and how to address them. We will link to that here when available.
We'll follow that with a technical blog post explaining the findings, the underlying causes, and the engineering changes we've made, again linked here when published.
If our assessment changes or we identify any additional steps customers need to take, we'll communicate those.
If you have questions about your particular environment, please contact Tailscale Support.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.