The OpenClaw BlueBubbles plugin is vulnerable to an authentication bypass, allowing unauthenticated attackers to send unauthorized webhook requests.

This vulnerability involves incorrect authorization where the BlueBubbles plugin trusts incoming webhook requests based solely on the TCP peer address, accepting loopback addresses as valid authentication even when the required webhook secret is missing. An unauthenticated attacker can trigger these requests if the service is reachable via a reverse proxy that does not enforce strong upstream authentication.

Successful exploitation allows an unauthenticated attacker to manipulate the BlueBubbles iMessage channel, potentially leading to unauthorized message processing or system interaction. With a CVSS score of 7.5, this issue represents a significant risk to the integrity of the communication flow within the AI assistant. Failure to remediate may lead to unauthorized data injection or control over the messaging integration.

Immediate Action: Update the OpenClaw and @openclaw/bluebubbles packages to version 2026.2.13 or later immediately.

Proactive Monitoring: Review access logs for unexpected webhook activity originating from local loopback addresses or unusual external traffic patterns targeting the BlueBubbles integration.

Compensating Controls: If immediate patching is not feasible, configure the deployment to require a non-empty, complex BlueBubbles webhook password and ensure any public-facing reverse proxies enforce strict authentication before forwarding traffic to the Gateway.

Public Exploit Available: No (exploit_available: false)

The reliance on network-level trust for authorization is a critical design flaw that exposes the application to unauthenticated command injection via webhooks. Organizations using the BlueBubbles plugin must prioritize the update to version 2026.2.13 to enforce proper secret-based authentication. Immediate deployment of the patch is necessary to eliminate this authorization bypass and secure the communication channel.