<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tailscale on CuraSec</title><link>https://curasec.metacog.co.kr/tags/tailscale/</link><description>Recent content in Tailscale on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 17:09:30 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/tailscale/index.xml" rel="self" type="application/rss+xml"/><item><title>Tailscale SSH Flaws Enable Lateral Root Access via Compromised Nodes</title><link>https://curasec.metacog.co.kr/insights/2026-10-28-tailscale-patches-ssh-flaws-that-could-let-hacked-devices-ga/</link><pubDate>Wed, 28 Oct 2026 17:09:30 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-28-tailscale-patches-ssh-flaws-that-could-let-hacked-devices-ga/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Any environment using Tailscale&amp;rsquo;s built-in SSH server has a lateral-movement exposure: a compromised node could pivot to root-level access on adjacent servers. No KEV or PoC signals, but the blast radius is high — update all Tailscale agents to 1.104.4 and audit which nodes have Tailscale SSH enabled.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or IOCs reported, so no immediate hunt work; file this as a lateral-movement technique to understand — a compromised Tailscale-managed host could be leveraged for stealthy root-level pivoting across the mesh, worth noting if Tailscale SSH appears in your estate.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Tailscale SSH flaws allow root privilege escalation, patch pending</title><link>https://curasec.metacog.co.kr/insights/2026-10-27-tailscale-warns-of-ssh-flaws-allowing-root-privilege-escalat/</link><pubDate>Tue, 27 Oct 2026 16:34:51 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-27-tailscale-warns-of-ssh-flaws-allowing-root-privilege-escalat/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Tailscale is widely deployed for zero-trust SSH in cloud environments; with no patch yet available and no exploitation evidence, disable the Tailscale SSH feature (distinct from standard SSH) on affected nodes now and schedule patching as soon as Tailscale releases a fix.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation, IOCs, or mapped TTPs are available yet; file this as context for future detection work once Tailscale publishes patch details and technical specifics about the exploit paths.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Assess whether your organization uses the Tailscale SSH feature specifically, and task the engineering team to disable it pending patch availability; root-level compromise of zero-trust networking tooling carries material exposure if later exploited.&lt;/li>
&lt;/ul></description></item><item><title>Unpatched Tailscale SSH Flaw Enables Root Pivot via Compromised Device</title><link>https://curasec.metacog.co.kr/insights/2026-10-26-unpatched-tailscale-ssh-flaws-could-let-a-hacked-device-reac/</link><pubDate>Mon, 26 Oct 2026 17:20:31 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-26-unpatched-tailscale-ssh-flaws-could-let-a-hacked-device-reac/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Tailscale is widely deployed for zero-trust networking, and this flaw enables root-level lateral movement within the mesh if SSH port forwarding is enabled. No patch or KEV yet — audit Tailscale SSH ACLs and disable port forwarding on sensitive nodes this quarter.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The attack path (pivot from one compromised Tailscale node to root on others via SSH port forwarding) is a useful lateral-movement model, but the truncated summary provides no IOCs or ATT&amp;amp;CK mappings to build detections from right now.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>