When tokenless Tailscale auth is enabled, OpenClaw should only allow forwarded-header auth for Control UI websocket authentication on trusted hosts. In affected versions, that tokenless path could also be used by HTTP gateway auth call sites, which could bypass token/password requirements for HTTP routes in trusted-network deployments.
openclaw (npm)<= 2026.2.19-2 (latest published npm version as of February 21, 2026)2026.2.21 releaseDeployments relying on token/password for HTTP gateway routes could be downgraded to tokenless behavior when Tailscale header auth is enabled. This weakens expected HTTP route authentication boundaries even in trusted-host network setups.
Per SECURITY.md, this does not affect the recommended setup: keep the Gateway loopback-only (or otherwise within a trusted host/network boundary), use Tailscale serve/funnel for remote access, and keep tokenless Tailscale auth scoped to Control UI websocket login.
allowTailscaleHeaderAuth, default false) in gateway auth.356d61aacfa5b0f1d5830716ec59d70682a3e7b8patched_versions is pre-set to the planned next release (2026.2.21) so once npm release is published, this advisory can be published directly without further field edits.
OpenClaw thanks @zpbrent for reporting.
{
"github_reviewed_at": "2026-03-03T18:43:04Z",
"nvd_published_at": null,
"cwe_ids": [
"CWE-290"
],
"severity": "MODERATE",
"github_reviewed": true
}