CVE-2026-32896

BlueBubbles webhook auth in the optional beta iMessage plugin allowed a passwordless fallback path. In some reverse-proxy/local routing setups, this could allow unauthenticated webhook events.

Affected Component and Scope

• Component: extensions/bluebubbles webhook handler
• Scope: only deployments using the optional BlueBubbles plugin where webhook password auth was not configured for incoming webhook events

Affected Packages / Versions

• Package: openclaw/openclaw (npm)
• Latest published npm version at triage time (2026-02-21): 2026.2.19-2
• Affected structured range: <=2026.2.19-2
• Fixed on main; planned patched release: 2026.2.21 (>=2026.2.21)

Details

The vulnerable implementation had multiple auth branches, including a passwordless fallback with loopback/proxy heuristics.

The fix now uses one authentication codepath:

• inbound webhook token/guid must match channels.bluebubbles.password
• webhook target matching is consolidated to shared plugin-sdk logic
• BlueBubbles config validation now requires password when serverUrl is set

Fix Commit(s)

• 6b2f2811dc623e5faaf2f76afaa9279637174590
• 283029bdea23164ab7482b320cb420d1b90df806

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.21) so once npm release is out, advisory publish can proceed without additional ticket edits.

OpenClaw thanks @zpbrent for reporting.

BlueBubbles is an optional beta iMessage plugin, and onboarding/channel-add flows already require a password. Practical exposure is mainly custom/manual configurations that omitted webhook password authentication.

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2026-32896 has a CVSS score of 4.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.21); upgrading removes the vulnerable code path.

Kodem intelligence

• Upgrade to a release that includes this patch (>=2026.2.21, planned).
• Ensure BlueBubbles webhook delivery includes a matching password (?password=<password> or x-password).

1. What is CVE-2026-32896? CVE-2026-32896 is a medium-severity missing authentication for critical function vulnerability in openclaw (npm), affecting versions < 2026.2.21. It is fixed in 2026.2.21. A critical operation is accessible without requiring any authentication.
2. How severe is CVE-2026-32896? CVE-2026-32896 has a CVSS score of 4.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32896? openclaw (npm) versions < 2026.2.21 is affected.
4. Is there a fix for CVE-2026-32896? Yes. CVE-2026-32896 is fixed in 2026.2.21. Upgrade to this version or later.
5. Is CVE-2026-32896 exploitable, and should I be worried? Whether CVE-2026-32896 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32896 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32896? Upgrade openclaw to 2026.2.21 or later.