OpenClaw has BlueBubbles webhook auth bypass via loopback proxy trust
openclaw · openclaw @openclaw/bluebubbles
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| openclaw npm |
|
|
| @openclaw/bluebubbles npm |
|
|
openclaw · openclaw @openclaw/bluebubbles
| Product | Affected | Fixed in |
|---|---|---|
| openclaw npm |
|
|
| @openclaw/bluebubbles npm |
|
|
OpenClaw is a personal AI assistant. Prior to 2026.2.13, the optional BlueBubbles iMessage channel plugin could accept webhook requests as authenticated based only on the TCP peer address being loopback (`127.0.0.1`, `::1`, `::ffff:127.0.0.1`) even when the configured webhook secret was missing or incorrect. This does not affect the default iMessage integration unless BlueBubbles is installed and enabled. Version 2026.2.13 contains a patch. Other mitigations include setting a non-empty BlueBubbles webhook password and avoiding deployments where a public-facing reverse proxy forwards to a loopback-bound Gateway without strong upstream authentication.
From the CVE record · GitHub_M
The optional BlueBubbles iMessage plugin can treat webhook requests from a loopback TCP peer as authenticated even when the configured webhook secret is missing or incorrect. An attacker who can send requests through a loopback connection, including via a public-facing reverse proxy, may bypass webhook authentication. The default iMessage integration is not affected unless BlueBubbles is installed and enabled.
Operators with BlueBubbles installed and enabled should check openclaw and @openclaw/bluebubbles npm packages older than 2026.2.13.