Executive brief
OpenClaw is a messaging/notification gateway used to integrate BlueBubbles with other platforms. When deployed behind a reverse proxy (nginx, Cloudflare Tunnel, ngrok, etc.), an attacker can send unauthenticated webhook requests that appear to come from localhost, bypassing password authentication. This allows remote attackers to inject fake messages and reactions into BlueBubbles conversations without knowing the webhook password.
Technical details
The vulnerability is a missing authentication check (CWE-306) in the BlueBubbles webhook handler. The handler accepts HTTP POST requests to the webhook endpoint and previously treated any request with a loopback remoteAddress (127.0.0.1, ::1, ::ffff:127.0.0.1) as automatically authenticated, without validating the configured webhook password or forwarding headers. When OpenClaw Gateway runs behind a reverse proxy, the proxy connects to the gateway over localhost, causing the gateway to see all proxied requests as coming from loopback and bypass authentication. An unauthenticated remote attacker who can reach the proxy endpoint can inject arbitrary BlueBubbles message/reaction events. The vulnerability requires network access to the reverse proxy endpoint and is most severe when the proxy is publicly exposed. Fix released in version 2026.2.12 removes loopback-based auth bypass and requires the configured webhook secret; a defense-in-depth follow-up will reject passwordless webhooks through proxies.
Affected products
- OpenClaw OpenClaw < 2026.2.12
Timeline
- 2026-02-17: disclosed
- 2026-02-12: patched: Version 2026.2.12 released with primary fix