Choose a display language

SPECIAL REPORT · 2026-10-25 23:18 JST

TailwormReview the boundaries
inside the network.

For Tailscale / headscale users.
Start with who has SSH access, and the privileges available after connecting.

What to check today ↓Watch the six-scene feature →

Cutoff 23:18 JST / 14:18 UTC. Primary sources were retrieved afterwards.
The research page and vendor response may change; they are not immutable copies of what was available at the cutoff.

Versions studied1.104.2 / 0.29.5Tailscale / headscale
VendorInvestigating and fixingAffected configurations under review
Tailworm-fixed versionNot confirmed in this reviewSeparate from the certificate update

01 / FIND YOUR EXPOSURE

Which features do you use?

This summarizes the researcher’s reproduction report. We did not run the PoC. The 11 headings include configuration and threat-model observations; they are not 11 assigned CVEs or 11 compromises.

SSH / FINDINGS 1–3, 5

Tailscale SSH

Requires authorized access to an SSH-enabled node and the relevant forwarding permissions. The report describes privilege-boundary crossings through root-owned Unix-socket operations and path races.

Check: enabled nodes, SSH rules and unnecessary forwarding
SELF-HOSTED / FINDING 6

headscale

The report describes memory exhaustion and cache eviction through public registration paths in 0.29.5. The researcher also says SSH forwarding cannot be suppressed.

Check: exposure, SSH grants, memory and registration monitoring
EXPERIMENTAL / FINDING 4

conn25 connectors

The finding says a device with the conn25 usage capability can choose the connector’s actual destination. Review routes into LANs, metadata services and clusters.

Check: conn25 use, permissions and actual destination egress
SERVE / FINDINGS 7–11

Serve / Funnel

Includes TCP forwarding to privileged sockets, post-configuration races, binding to all interfaces and authorization across multiple mounts. Conditions depend on operator configuration and application authorization.

Check: forwarding rules, listen scope and backend authorization

DERP-client memory exhaustion requires connecting to a malicious relay. Do not assume every user is exposed through the same path. Finding-by-finding details and caveats →

02 / ACT TODAY

Check access, then narrow permissions.

  1. Inventory actual SSH reachability. Limit access to the users, devices and destinations that need it, and remove unnecessary forwarding. Distinguish ordinary OpenSSH connections from Tailscale SSH.
  2. Consider temporarily disabling SSH on sensitive hosts. Verify an alternative management path first. Specifying a non-root user alone does not establish protection against this privilege escalation. This is not a vendor recommendation for a universal shutdown.
  3. Do not call check mode a fix. Additional entry authentication helps, but does not repair privilege issues inside an authorized session.
  4. Review headscale, connectors and Serve separately. Check public registration paths, memory limits, unnecessary conn25 permissions and privileged-socket forwarding. IP firewalls cannot stop local Unix-socket races. Verify Kubernetes egress controls against the actual path.
  5. Match updates to official advisories. Enable automatic updates where suitable and track confirmed fixes. Keep tested versions, fixed versions and configuration mitigations separate.

Read-only starting points. Do not publish secrets from command output or configuration.

tailscale version
tailscale serve status
tailscale funnel status

Also check enabled nodes and SSH policy in the admin console and deployment configuration. Official CLI reference / Official SSH documentation

03 / IF COMPROMISE IS SUSPECTED

Rebuild and revoke identities.

Isolate and preserve evidence, remove or revoke the device through the control plane, and rotate exposed enrollment keys and API credentials. For root compromise, investigate whether state was copied. Reinstalling the OS alone does not revoke exfiltrated keys. If a signing node was affected, also assess Tailnet Lock keys.

Researcher’s containment guidance / Official device removal

04 / A DIFFERENT FIX

Updating to 1.104.2
does not complete Tailworm remediation.

Version 1.104.2, released 10/21, addresses TS-2026-013 and the separate eMudhra certificate issue. The Tailworm research also targets that version. Apply the certificate update while tracking a confirmed Tailworm fix separately.

Tailscale security bulletins / Changelog / headscale releases

Separate research findings from established facts.

Researcher: Erica Windisch / Cyberdione Labs. Testing ran 10/22–24 against Tailscale 1.104.2 and headscale 0.29.5. We have not independently reproduced the findings in a real deployment. The vendor is investigating affected configurations; this is not individual confirmation of all 11 findings. Dedicated CVEs, CVSS ratings and minimum fixed versions remain unconfirmed in this review.

The research site’s exact revision history and the vendor Reddit response’s edit time are unresolved. Do not backdate later-retrieved information into a confirmed state before 23:18. Records, hashes and research limitations remain in the repository.