In affected versions, 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.
openclaw < 2026.2.13@openclaw/bluebubbles < 2026.2.13If a deployment exposes the BlueBubbles webhook endpoint through a same-host reverse proxy (or an attacker can reach loopback via SSRF), an unauthenticated party may be able to inject inbound webhook events into the agent pipeline.
Thanks @MegaManSec (https://joshua.hu) of AISLE Research Team for reporting.
{
"github_reviewed_at": "2026-02-17T21:33:51Z",
"nvd_published_at": "2026-02-19T22:16:47Z",
"severity": "HIGH",
"cwe_ids": [
"CWE-863"
],
"github_reviewed": true
}