openclaw
Affected
- introduced
0, fixed2026.2.21(semver)
Fixed versions
2026.2.21
Fix
- Fixed version
2026.2.21npm install [email protected]
Advisory
Also known as: CVE-2026-32045
OpenClaw's gateway tokenless Tailscale auth applied to HTTP routes
Summary
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.
Affected Packages / Versions
openclaw (npm)<= 2026.2.19-2 (latest published npm version as of February 21, 2026)2026.2.21 releaseImpact
Deployments 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.
Fix
allowTailscaleHeaderAuth, default false) in gateway auth.Fix Commit(s)
356d61aacfa5b0f1d5830716ec59d70682a3e7b8Release Process Notepatched_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.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.21 (semver)2026.2.21
2026.2.21npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0