Openclaw cli: OpenClaw has a webhook auth bypass when gateway is behind a reverse proxy (loopback remoteAddress trust) (CVE-2026-29613)

The BlueBubbles webhook handler in OpenClaw CLI versions prior to 2026.2.12 treats any request with a loopback socket remoteAddress as authenticated, without validating forwarding headers. When the OpenClaw Gateway is behind a reverse proxy (such as Tailscale Serve/Funnel, nginx, Cloudflare Tunnel, or ngrok), the proxy connects over loopback, causing the gateway to accept unauthenticated remote requests. This allows an attacker with access to the proxy endpoint to inject arbitrary inbound BlueBubbles message or reaction events. The vulnerability is fixed in version 2026.2.12 by removing the loopback-based authentication bypass and enforcing the configured webhook secret. A defense-in-depth update further improves handling of proxied requests in subsequent releases.

An attacker who can reach the reverse proxy endpoint can bypass webhook authentication and inject arbitrary BlueBubbles message or reaction events. This impacts the integrity of inbound events processed by the BlueBubbles webhook handler. There is no direct confidentiality or availability impact reported. The vulnerability only affects deployments exposing the BlueBubbles webhook endpoint behind a reverse proxy and having vulnerable OpenClaw versions.

A patch is available in OpenClaw CLI version 2026.2.12 that removes the loopback-based authentication bypass and requires the configured webhook secret. Users should upgrade to version 2026.2.12 or later. Additionally, ensure a BlueBubbles webhook password is configured and avoid exposing the gateway webhook endpoint publicly without authentication. The vendor plans further defense-in-depth improvements in releases following 2026.2.12.