Changelog

• When checking the device posture status of a machine on the Machines page of the admin console, you can see the assertions the posture requires, each machine's value, and whether it's passing. For each posture, you can also see a count of policy file rules that affect a machine and require this posture.

• The Tailscale GitHub Action properly skips re-downloading binaries on linux if a file with a matching SHA already exists.
• The Tailscale GitHub Action groups log output by default. Use the log-mode parameter to control whether the logging output is grouped, ungrouped, or run in "quiet" mode.

A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.

• ProxyGroup reconciler no longer triggers on incorrect events.

All Platforms

• Resolved an issue that could cause a loss in connectivity when a netmap update occurs near the time of reauthentication.

macOS

• Resolved an issue that could prevent exit nodes from appearing when using a custom coordination server.

iOS

• Resolved an issue that could prevent exit nodes from appearing when using a custom coordination server.

tvOS

• Resolved an issue that could prevent exit nodes from appearing when using a custom coordination server.
• Resolved an issue that prevented the VPN tunnel from automatically starting on a cold boot.

Use Tailscale Privileged Access Management (PAM) (beta) to provide application-aware access to resources in your Tailscale network.

• Services can be defined for privileged access, including SSH, database, RDP, HTTPS, Kubernetes, and Amazon S3 types.
• Sessions can be recorded for SSH, database, HTTPS, and Kubernetes Service types.
• Policies can be set for user access and in-service permissions through grants.
• Secrets store can be linked for credential injection.
• Logs of user access can be viewed, and session recordings can be played back.
• Connectors can be managed and deployed to provide connectivity to services.
• Browser client permits access to services without requiring a Tailscale client download.
• Custom domain management can be used for public HTTP PAM services.
• Custom Amazon S3 bucket can be configured for PAM recording storage.
• Service accounts can be created for machine identities to interact with the PAM API.

Request access to join the Tailscale PAM beta.

Use Aperture (generally available) to secure and manage AI agents and LLM sessions with cost controls, request and response hooks, guardrails, logging, MCP support, and API proxying.

• A promotional model token credit is included for use with new and existing Aperture gateways.
• Model tokens can be purchased directly in Aperture for major AI models.
• With user approval, Aperture can add nodes to your tailnet with the Tailscale MCP endpoint for Aperture and coding agents.
• Tailnet nodes can be accessed through Tailscale SSH with the SSH MCP endpoint after approval.
• Chat Projects can be used to share instructions, tool access, and tailnet nodes in group chats.
• Baseline tool access can be defined across Aperture chats with default tool permissions.

All Platforms

• Go is updated to version 1.26.6.
• Tailscale refuses host-scoped IPv4 destinations at every point that acts on an unmapped 4via6 address. This fix addresses a security vulnerability described in TS-2026-011.
• When MagicDNS is disabled, unqualified hostnames are correctly forwarded to the configured nameservers.
• Resolved an issue where nodes with Tailnet Lock enabled on large tailnets would experience startup failures.

Windows

• Resolved an issue where the Windows installer would fail during an upgrade when the name of the user's home directory contained a space.
• tailscaled returns an error instead of panicking on devices where IPv6 or NetBios over TCP/IP is disabled.

iOS

• Memory usage is reduced for iOS devices on large tailnets.

tvOS

• Memory usage is reduced for tvOS devices on large tailnets.

A new release of the Tailscale container image is available. You can download it from Docker Hub or from our GitHub packages repository.

• The container waits longer for its initial connection to the coordination server when you set the new TS_BOOT_TIMEOUT environment variable. It accepts a duration, such as 90s or 3m, and defaults to 60s.

A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.

• Peer relays on AWS are reachable regardless of the availability zone their pod is scheduled in. Pinning Elastic IPs also requires pinning the pods to the same zone using a ProxyClass.
• Network Load Balancers fronting peer relays on AWS use HTTP instead of TCP for pod health checks. Peer relays listen only on UDP, so the default TCP health check could never succeed, causing every target to be reported as unhealthy.

• The list tailnets endpoint paginates results. By default, organizations with more than 100 tailnets now receive only the first 100 results, with totalCount and cursor parameters to retrieve additional results.
• limit and cursor query parameters are supported on the list tailnets endpoint. If no limit is specified, the endpoint returns 100 results per page. Use the returned cursor value as the next request's cursor parameter to retrieve the next page until the returned cursor value is empty.

A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.

• PeerRelays are deployable in-cluster via a custom resource.
• Annotations can now be applied to the operator's deployment resource via Helm.
• Workload identity federation can now be configured for the Tailnet custom resource.
• 4via6 is supported in connector and egress proxy resources when egressing from a dual-stack cluster.
• IPv6 is supported in Egress ProxyGroups.
• Operator log output excludes superfluous entries, such as entries for resources that do not contain annotations.
• Several log lines have adjusted log levels.
• MTU values are clamped on both the input and output interfaces, where previously only the output interface was clamped.
• ProxyGroup services no longer fail to reconcile when using the same hostname across multiple tailnets.
• ProxyGroup static endpoints no longer cause constant reconciliation loops due to non-deterministic ordering.
• DNS reconciler no longer drops reconcile events, which left the dnsrecords ConfigMap stale.
• EndpointSlices for Egress ProxyGroup are verified on every reconcile.
• Cert renewal retries follow Let's Encrypt's recommended backoff schedule instead of a fixed interval.
• Let's Encrypt Retry-After headers are honored by Kubernetes proxies when hitting rate limits, which avoids the tight retry loops that made rate-limit backoffs worse.
• Per-attempt cert issuance timeout in Kubernetes proxies is increased to 30 minutes, giving ACME challenges room to complete under load without failing prematurely.
• Cert issuance attempts no longer run against a VIPService that is being torn down during Ingress deletion, which wasted Let's Encrypt rate-limit quota.

A new release of the Tailscale container image is available. You can download it from Docker Hub or from our GitHub packages repository.

This version contains no changes except for library updates.

A new release of the Tailscale tsrecorder is available. You can download it from Docker Hub.

• Recorder does not attempt to index empty recording placeholder files on startup.

All Platforms

• A regression causing incoming Tailscale Funnel connections to fail is resolved.

All Platforms

• tailscaled_serve_outbound_bytes_total and tailscaled_serve_inbound_bytes_total client metrics report bytes sent to and received from peers on Tailscale Serve connections for Tailscale Services.
• The tailscale get CLI command returns the current node's preferences.
• The tailscale whoami CLI command displays information about the current user and device.
• The tailscale service list CLI command displays Tailscale Services visible to the current node.
• Node additions and removals are processed in constant time, significantly reducing CPU usage on large tailnets. This currently applies to all platforms except Windows.
• Tailscale Funnel domains use TLS-ALPN-01 for faster HTTPS certificate renewals.
• Deprecated formats for 4via6 MagicDNS names are no longer available to use.
• TLS certificates on idle servers proactively auto-renew in the absence of traffic. Warnings are issued when there is no valid cached certificate.
• Dials to dual-stack DNS names through an IPv4-only exit node connect to the correct address when using tailscaled in userspace mode.
• Certificate issuance for multiple domains runs in parallel. Provisioning multiple domains does not stall each certificate behind the previous one.
• Resolved an issue causing connectivity issues from the operating system waking from sleep in wireguard-go.
• A node's home DERP region is reported to the coordination server after a profile switch or login, allowing for peers to immediately connect to the node.
• A memory leak that occurred after a failed WireGuard handshake has been resolved.
• tailscale status --peers=false command shows the current device name in the output.
• Resolved an issue that prevented connectivity via Tailscale Peer Relays after a client restart.
• Tailscale SSH passes environment variables to child processes via inherited file descriptors. This fix addresses a security vulnerability described in TS-2026-010.

Linux

• Assembly crypto routines for 32-bit ARM are available, improving performance on these platforms.
• Userspace TUN optimizations improve throughput and performance.
• Resolved an issue impacting performance of UDP GSO on Linux v7.0.x through v7.1.4.

macOS

• The Tailscale protocol handler supports deep-linking to devices, exit nodes, and settings panels in the application window.
• The device list in the menu bar and Windowed UI loads more efficiently.
• The client onboarding process is redesigned to match the style of the windowed UI.
• Exit node names appear as subtitles in Shortcuts and can be used to filter the list of displayed exit nodes.
• The connection toggle is disabled when Tailscale is controlled by VPN On Demand settings for the active network interface.
• Domain matching on-demand rules are evaluated in the correct order.
• A mismatch between the active exit node and the suggested exit node when using automatic exit node selection has been resolved.
• tailscale configure kubeconfig checks permissions on the $KUBECONFIG file before refusing to write to it when it's in a non-standard directory, fixing false rejections during Kubernetes API server access setup.

iOS

• A new split-plane layout is used on iPad in both portrait and landscape orientation and on sufficiently wide iPhones in landscape.
• The status widget supports toggling the active exit node inline.
• Exit node names appear as subtitles in Shortcuts and can be used to filter the list of displayed exit nodes.
• The connection toggle is disabled when Tailscale is controlled by VPN On Demand settings for the active network interface.
• Domain matching on-demand rules are evaluated in the correct order.
• A mismatch between the active exit node and the suggested exit node when using automatic exit node selection has been resolved.

tvOS

• The Tailscale web client is supported for remote management of Apple TV devices.
• The client onboarding process ensures the VPN configuration is approved and a login profile is added before using fast user switching.
• tvOS does not require a restart to use a custom coordination server defined in Settings.

Android

• A single CGNAT route is created when no other interface is using CGNAT.
• TCP connections do not reset when VPN routing changes due to a netmap update.
• Health warnings are promptly cleared as soon as the underlying issue is resolved.

Synology

• ARMv7 binaries with software floating point are produced for certain Synology NAS models, replacing older ARMv5 binaries.

• Use the tailnet creation API to create, list, and delete API-only tailnets in your organization (alpha).

All Platforms

• Tailscale SSH Unix socket forwarding respects symlink permissions. This fix addresses a security vulnerability described in TS-2026-004.
• Tailscale SSH performs additional checks to disallow UIDs and numeric-only usernames. This fix covers additional scenarios described in TS-2026-006.

• The Tailscale admin console is now available at console.tailscale.com. Authentication continues to use login.tailscale.com, and requests to login.tailscale.com/admin/ automatically redirect to the new subdomain.

All Platforms

• Tailscale Serve Unix socket proxy targets are restricted to the root user. This fix addresses a security vulnerability described in TS-2026-005.
• Tailscale SSH does not allow the use of UIDs or numeric-only usernames. This fix addresses a security vulnerability described in TS-2026-006.
• Nodes advertising Tailscale Services filter and reject packets from service IPs on ports they do not advertise. This fix addresses a security vulnerability described in TS-2026-007.
• Tailscale Serve and Tailscale Funnel terminate path walks for non-absolute paths, preventing CPU core pinning. This fix addresses a security vulnerability described in TS-2026-008.
• Tailscale SSH does not allow the use of usernames with leading dashes. This fix addresses a security vulnerability described in TS-2026-009.
• An issue where a user could be logged out of Tailscale when changing the tag on a device via CLI has been resolved.
• An issue that could cause a crash on 32-bit ARM platforms is resolved.

• Microsoft Entra ID and Google Workspace group sync includes members of nested groups.

• Users with the Owner role can switch their tailnet's identity provider from the admin console for supported providers (beta).

• Create and manage OAuth Apps for Device Provisoning with the Tailscale API (alpha).

Note: 1.98.6 and 1.98.7 were release candidates intended for testing only.

All Platforms

• An issue causing connectivity disruptions when the operating system wakes from sleep in wireguard-go is resolved.
• An issue causing excessive handshake initiation retries in wireguard-go is resolved.
• An issue causing connection leaks in Tailscale SSH Session Recording is resolved.

• ip:publicAddress device posture attribute is available for use in postures and viewable on the Machines page of the admin console. To test, go to the Settings page of the admin console and toggle Public IP addresses for device posture (beta).

• The Tailnet system policy accepts a comma-separated list of tailnet IDs or organization IDs.

• Tailscale network flow logs and configuration audit logs can be streamed to Azure Blob Storage.

• Use identity-aware connectors to let agents and users reach your data via MCP and API endpoints (alpha).
  • Tailnet access controls apply to every request, giving you one identity system across the chat interface and any agent connected to your tailnet.
• Use Aperture chat, a mobile-responsive chat interface that enables switching between multiple LLMs with support for MCP, API connectors, and sandboxes (alpha).
• Use sandboxes to let agents use a computer for chat-based tasks and coding, hosted by Tailscale or integrated with Tailscale identity from a third party (alpha).
  • Run sandboxes ephemerally from chat or as longer-running, workstation-like environments. Sandbox support is a private alpha. Request access to join.

• Configure devices in your tailnet to receive group membership information from the Tailscale control plane (alpha).

All Apple Platforms

• macOS and iOS clients are now built using the Xcode 26.5 toolchain.

A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.

• The operator no longer fails to perform token exchanges when using workload identity
• Ingress & Egress ProxyGroup pods now correctly clamp their MTU values

• Preset apps are available for Oracle Cloud Infrastructure (OCI), including per-region compute and networking, per-region Object Storage, and a global preset for the Oracle Services Network (OSN).

All Platforms

• An issue causing a deadlock when processing peer changes and disconnecting from the Tailscale control server is resolved.

v0.29.2 of the Tailscale Terraform Provider has been released with the following changes:

• A regression in tailscale_tailnet_key has been resolved where recreate_if_invalid was not being checked before recreating the resource when the key is not found.

A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.

• New: The DNSConfig custom resource supports specifying node affinity rules and node selectors for nameserver pods.
• The operator Helm chart supports priority class names for operator pods.
• The operator now reconciles Services and Ingresses with names longer than 63 characters.
• ProxyGroup egress services now obtain an IPv4 address in addition to a IPv6 address on dual-stack clusters.
• API server proxy ProxyGroup pods request a new auth key when required.

A new release of the Tailscale tsrecorder is available. You can download it from Docker Hub.

• Recorder pods can request a new auth key when required.

Linux

• An issue where netfilter rules could be applied inconsistently after a netfilter mode change failed has been resolved. Connmark and CGNAT rules are applied after the active netfilter mode is successfully updated, matching the behavior of other netfilter paths.

A new release of the Tailscale container image is available. You can download it from Docker Hub or from our GitHub packages repository.

This version contains no changes except for library updates.

Use Aperture CLI (alpha) to launch and manage coding agents with Aperture's built in guardrails, policy enforcement, and observability. Aperture CLI supports Claude Code, Gemini CLI, OpenCode, OpenAI Codex, Copilot CLI, and Claude Cowork, on devices both inside and outside your tailnet.

• Manage domain verification and domain aliases for your tailnet using the Domains page of the admin console.

v0.29.1 of the Tailscale Terraform Provider has been released with the following changes:

• The tailscale_tailnet_key resource no longer clears the key attribute when Terraform state is refreshed. tailscale_tailnet_key values that are already cleared should be recreated to generate a new key in state. This issue only affects tailscale_tailnet_key resources that were refreshed on v0.29.0 of the Tailscale Terraform provider.
• The tailscale_tailnet_key resource no longer causes a panic when a key has been removed outside of Terraform.

All Platforms

• Go is updated to 1.26.3.
• A regression from 1.98.0 is patched, ensuring MagicDNS resolves tailnet hostnames after a network change. Windows clients are unaffected.

v0.29.0 of the Tailscale Terraform Provider has been released with the following changes:

• Use the tailscale_service resource and tailscale_service data source to manage Tailscale Services.
• Set identity_token_environment_variable_name in the provider to specify the environment variable to read an identity token from. This is useful for platforms like HCP Cloud that have well-known environment variable names for the identity token.
• Obtain an OIDC identity token from the runtime environment by setting audience in the provider. This is useful for runtimes like GitHub Actions, AWS via EC2 IMDSv2 or ECS, or GCP via Metadata Server.
• Read credential related provider argument values from disk by supplying paths prefixed with file:.
• The provider has migrated from Terraform Plugin SDKv2 to the Terraform plugin framework.
• The tailscale_federated_identity resource no longer accepts an empty string ("") for the audience argument, to match the server-side validation for it. Omit the audience argument or set it to null to let Tailscale generate the audience (recommended), or set it to a non-empty string to specify it yourself.

• All plans can purchase additional tagged resources above the included 50-device limit.
• All plans can view the number of tagged resources in their tailnet that count against the usage limit.

Note: 1.98.0 was a release candidate intended for testing only.

All Platforms

• Expired preferred peer addresses are cleared, reducing the time to elect an alternative.

Linux

Note: 1.98.1 introduced a regression in the interaction between Tailscale and MagicDNS on Linux. The Linux release has been withdrawn pending a fix.

• IP forwarding for subnet routers and exit nodes is reported as a health check, surfacing warnings when misconfigured.
• src_valid_mark sysctl is set in addition to connmark firewall rules to improve reverse path filtering and prevent dropped packets.

macOS

• Devices and exit nodes can be searched from the application's main menu on macOS Tahoe 26 or later.
• The AppIntroShown system policy disables the Welcome to the Tailscale app modal window introduction that appears when you log in to Tailscale on a device for the first time.
• The Hide Dock Icon checkbox in Settings is available when Tailscale is disconnected.
• The tailscale drive CLI command directs users to configure Taildrive through the client GUI instead of returning an error.
• Device list is more responsive, especially for larger tailnets.

iOS

• iOS devices can be used as exit nodes.
• Device list is more responsive, especially for larger tailnets.

• View the device posture status of a machine in your tailnet by using the Machines page of the admin console.

A new release of GitOps for Tailscale with GitHub Actions is available. You can download it from the GitHub Actions Marketplace.

• Update dependencies to remove Node 20 deprecation warning.

Use Aperture (beta) to secure and manage your LLM agents with a single control plane across all your providers and models.

• Create custom guardrails with pre-LLM-call hooks to strip or block PII and restrict specific agent tools before requests reach the LLM.
• Configure log retention time down to zero for request/response capture logs, with S3-compatible export supported.
• Audit logs for configuration changes and when admins view logs owned by other users are available using a new API endpoint and UI.
• Set customizable quotas across providers, models, users, agents, or individual agent runs.

• API-only tailnets can be accessed by any OAuth client with the all scope in the creating tailnet.

• A seat calculator is available to help you understand seat consumption on your account before upgrading to a new plan.

• New tailnet plan signups are billed based on occupied user seats instead of monthly active users. Existing tailnets on a legacy plan will continue to be billed based on monthly active users.
• All plans can have an unlimited number of user devices in a tailnet.
• The Personal plan provides up to six free users instead of the previous three users.
• Ephemeral node usage is free up to a monthly limit, by pricing plan. After four hours in the tailnet, nodes are treated as standard tagged devices and stop consuming ephemeral minutes.
• As part of the Personal plan change, Aperture by Tailscale also provides for up to six free users during the alpha testing phase.
• The Starter plan is no longer available as a plan option for new signups. The new Standard plan is the closest equivalent option.
• Promo codes can be applied to existing plans. Previously, promo codes could only be applied when upgrading to a new plan.

For more information about our pricing plans and the features available for each plan, refer to Pricing and Pricing FAQs.

A new release of the Tailscale container image is available. You can download it from Docker Hub or from our GitHub packages repository.

• Services are now automatically advertised on startup. This can be disabled by setting the new environment variable, TS_EXPERIMENTAL_SERVICE_AUTO_ADVERTISEMENT, to false.
• The Tailscale container no longer tries to create a secret using TS_KUBE_SECRET when the variable is empty.

A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.

• Ingress and Egress ProxyGroup pods are able to request a new authkey when required.
• Multiple tailnet access can be enabled with the use of the new Tailnet custom resource.
• ProxyGroup creation controls can be managed by namespace with the new ProxyGroupPolicy custom resource.
• The environment variable TS_EXPERIMENTAL_KUBE_API_EVENTS is removed. This can instead be set via Tailscale ACLs.
• The environment variable TS_LOCAL_ADDR_PORT no longer fails when it is populated with an IPv6 address without brackets.

A new release of the Tailscale tsrecorder is available. You can download it from Docker Hub.

• The Recorder CRD defaults to deploying a single replica StatefulSet, using the filesystem storage backend`.

iOS

• An issue that could cause the network extension to encounter an out of memory condition on large tailnets is resolved.

tvOS

• An issue that could cause the network extension to encounter an out of memory condition on large tailnets is resolved.

Linux

• An issue on forks of Linux caused by fallback-on-ENOSYS logic is resolved.
• An issue that could cause a segmentation violation during startup on MIPS devices is resolved.

Android

• An issue causing a deadlock when disconnecting from a tailnet is resolved.

Synology

• An issue on forks of Synology Linux caused by fallback-on-ENOSYS logic is resolved.

Windows

• DNS resolution issue caused by NRPT rule formatting is resolved.

Note: 1.96.0 and 1.96.1 were release candidates intended for testing only.

All Platforms

• tailscale dns query|status command supports --json flag to return JSON output.
• tailscale wait [flags] command waits for Tailscale resources to become available for binding.
• tailscale ip command supports --assert=<specific-ip-address> flag to assert that one or more of the node's IP addresses matches the specified IP address.
• tailscale version --track and tailscale update --track support release-candidate flag to check for and update to release candidate builds.
• For 1.96.x, Go is updated from version 1.25 to 1.26.
• Tailscale Peer Relays advertise addresses discovered via Amazon EC2 Instance Metadata Service.
• tailscaled_peer_relay_endpoints gauge user metrics are available for Tailscale Peer Relays.
• The AuthKey system policy applies only when a user is not in a logged in state.
• UPnP routes as expected during long lived port mapping sessions scenarios, including hard NAT.

Linux

• Launch the systray application on startup using autostart file with the tailscale configure systray --enable-startup=freedesktop command.
• Scaling of Tailscale Peer Relays UDP sockets is gated by container-aware GOMAXPROCS defaults.
• Firewall rules created on Linux platforms correctly mark their traffic, avoiding reverse path filtering dropping connections and producing health warnings and risk prompts.
• OpenWrt versions 25.12.0 or later using apk as a package manager supports Tailscale updates.

macOS

• Windowed UI mode for macOS is generally available.
• Double-click an account in the Accounts section to switch to that account.
• A progress dialog indicates Tailscale is waiting on the browser to complete reauthentication.
• The open source variant of Tailscale on macOS sets the node:osVersion attribute.
• The Taildrop Send File action and shortcut do not transmit empty files on macOS Tahoe (version 26) or later.
• Tailscale data directories for the macOS standalone version are excluded from Time Machine backups.
• An issue that required a machine reboot after installing a Tailscale update is resolved.

iOS

• iOS bug report ID displays in its entirety instead of being truncated.
• The Taildrop Send File action and shortcut do not transmit empty files on iOS version 26 or later.

• Use workload identity federation (generally available) to authenticate Tailscale API requests with federated OIDC workload identities from third-party providers.