NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · OpenClaw

CVE-2026-32006: OpenClaw has a BlueBubbles group allowlist mismatch via DM pairing-store fallback

mediumCVSS 4.0 5.3 · 3.1 4.3GHSA-25pw-4h6w-qwvm

OpenClaw 2026.2.25 and earlier can treat a sender who is only DM-paired as allowed in BlueBubbles groups. This happens when `dmPolicy=pairing` and `groupPolicy=allowlist`. The sender passes the group check without being in `groupAllowFrom`. The fix is in OpenClaw 2026.2.26.

Published Mar 3, 2026 · Updated Mar 30, 2026 · Analysis Oct 31, 2026

What an attacker can do

OpenClaw's BlueBubbles channel keeps separate lists for direct messages and groups. With dmPolicy=pairing, identities approved in DMs live in a pairing store. In the vulnerable code, those pairing-store identities flowed into the group authorization decision. A person who had paired in a DM, but was never listed in groupAllowFrom, could pass the group sender check for both messages and reactions.

The practical result is that a group the operator meant to restrict accepts input from more people than intended. Those people can send messages the agent will act on, or reactions it will process. The attacker needs an existing DM pairing, so a low privilege is already required, and the CVSS vectors rate the effect as limited integrity impact (CWE-863).

The advisory is explicit about the limits. It does not bypass gateway auth or sandbox boundaries, and it grants no host-level privilege beyond what DM authorization already gave the sender. Only deployments with BlueBubbles, groupPolicy=allowlist, dmPolicy=pairing and at least one pairing-store entry are affected.

Who is affected

The openclaw npm package at 2026.2.25 and earlier is affected, but only when BlueBubbles is configured with groupPolicy=allowlist and dmPolicy=pairing and the pairing store has entries. Check the installed version:

npm ls openclaw

Then review the BlueBubbles channel settings in your OpenClaw configuration for both policy values.

openclaw

Ecosystem
npm
Affected
<= 2026.2.25
Fixed in
2026.2.26
Check
npm ls openclaw

How to fix it

Upgrade to openclaw 2026.2.26.

npm install [email protected]

The advisory says the fix centralizes DM and group authorization in shared resolvers, so channels no longer recompose the lists themselves. It adds regression tests for message and reaction ingress across channels. It also adds a CI check, lint:auth:no-pairing-store-group, that blocks pairing-store identities from entering group auth. The advisory lists no workaround. As a stopgap, review who is in your pairing store and remove entries that should not reach groups.

How to tell if you were hit

Compare the senders of group messages and reactions handled by BlueBubbles against groupAllowFrom. Any sender who appears in the pairing store but not in groupAllowFrom and still got through is an instance of this flaw. Review the pairing-store entries for people you did not mean to give group access. If an AI agent acts on those group messages, check its recorded actions for ones that came from such senders. Beam records agent shell commands, file access and MCP tool calls, which helps you see what the agent did after an unauthorized message.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

In [email protected], BlueBubbles group authorization could incorrectly treat DM pairing-store identities as group allowlist identities when dmPolicy=pairing and groupPolicy=allowlist.

A sender that was only DM-paired (not explicitly present in groupAllowFrom) could pass group sender checks for message and reaction ingress.

Per OpenClaw's SECURITY.md trust model, this is a constrained authorization-consistency issue, not a multi-tenant boundary bypass or host-privilege escalation.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published npm version at triage time: 2026.2.25
  • Affected versions: <= 2026.2.25
  • Patched versions: >= 2026.2.26 (planned next release)

Technical Details

Root cause was DM/group allowlist composition where DM pairing-store identities could flow into group authorization decisions.

Fix approach:

  • centralize DM/group authorization composition via shared resolvers
  • remove local DM/group list recomposition at channel callsites
  • add cross-channel regression coverage for message + reaction ingress
  • add CI guard to block future pairing-store leakage into group auth composition

Impact

  • Affects deployments using BlueBubbles with groupPolicy=allowlist and dmPolicy=pairing when pairing-store entries are present.
  • Could allow DM-authorized identities to be treated as group-authorized without explicit groupAllowFrom membership.
  • Does not bypass gateway auth, sandbox boundaries, or create new host-level privilege beyond existing DM authorization.

Fix Commit(s)

  • 051fdcc428129446e7c084260f837b7284279ce9

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.26) so once npm 2026.2.26 is published, this advisory can be published without further content edits.

OpenClaw thanks @tdjackey for reporting.

Credited to tdjackey.

Questions

Does this bypass OpenClaw's gateway authentication?

No. The advisory says it does not bypass gateway auth or sandbox boundaries and gives no host-level privilege beyond existing DM authorization.

Which configuration is vulnerable?

BlueBubbles with groupPolicy=allowlist and dmPolicy=pairing, when the pairing store has entries, on openclaw 2026.2.25 or earlier.

Is CVE-2026-32006 fixed?

Yes, in openclaw 2026.2.26. Fix commit 051fdcc moves DM and group authorization into shared resolvers.

Is it exploited in the wild?

No source reports exploitation, and the entry is not in CISA's KEV catalog.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries