openclaw
Affected
- introduced
0, fixed2026.2.12(semver)
Fixed versions
2026.2.12
Fix
- Fixed version
2026.2.12npm install [email protected]
Advisory
Also known as: CVE-2026-29613
OpenClaw has a webhook auth bypass when gateway is behind a reverse proxy (loopback remoteAddress trust)
Summary
The BlueBubbles webhook handler previously treated any request whose socket remoteAddress was loopback (127.0.0.1, ::1, ::ffff:127.0.0.1) as authenticated. When OpenClaw Gateway is behind a reverse proxy (Tailscale Serve/Funnel, nginx, Cloudflare Tunnel, ngrok), the proxy typically connects to the gateway over loopback, allowing unauthenticated remote requests to bypass the configured webhook password.
This could allow an attacker who can reach the proxy endpoint to inject arbitrary inbound BlueBubbles message/reaction events.
Affected Packages / Versions
openclaw (npm)< 2026.2.12>= 2026.2.12Exposure / Configuration
Details
The BlueBubbles webhook handler accepts inbound events via an HTTP POST endpoint under the configured BlueBubbles webhook path.
In vulnerable versions, the handler would accept requests as authenticated if req.socket.remoteAddress is loopback, without validating forwarding headers. With common reverse-proxy setups, the gateway sees the proxy as the direct client (loopback), even when the original request is remote.
Fix
2026.2.12): remove loopback-based authentication bypass and require the configured webhook secret.Fix Commit(s)
2026.2.12)Mitigations
Thanks @simecek for reporting.
High Basis: The source's own band: HIGH
0, fixed 2026.2.12 (semver)2026.2.12
2026.2.12npm 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