CVE-2026-53860

Description

### Summary BlueBubbles sender policy could match mutable conversation identifiers. In affected versions, a participant able to influence conversation-level identifiers could match an allowlist entry through conversation metadata rather than a stable sender identity. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable, this could receive agent responses that should have been limited to a configured sender. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path. ### Patched Versions The first stable patched version is `2026.5.7`. ### Mitigations prefer stable sender identifiers and keep BlueBubbles groups restricted until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

How to fix CVE-2026-53860

To remediate CVE-2026-53860, upgrade the affected package to a fixed version below.

• —upgrade to 2026.5.7 or later

Is CVE-2026-53860 being exploited?

No exploitation signal available. Neither CISA KEV nor a current EPSS score has been published for CVE-2026-53860.

Affected packages (1)

• from 0, < 2026.5.7

CVSS scores

References (4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-53860
• PATCHgithub.com/openclaw/openclaw
• WEBgithub.com/openclaw/openclaw/security/advisories/GHSA-8j37-5w68-wj2g
• WEBwww.vulncheck.com/advisories/openclaw-sender-policy-bypass-via-mutable-conversation-identifiers-in-bluebubbles