OpenClaw BlueBubbles Plugin Vulnerability: Pairing/Allowlist Mismatch

openclaw Updated 04 Mar 2026

Summary

04/03/2026
MODERATE
Yes i
Moderate
5.3

GHSA-jwf4-8wf4-jf2m: OpenClaw: BlueBubbles (optional plugin) pairing/allowlist mismatch when allowFrom is empty. Affects openclaw versions < 2026.2.22. Fixed in 2026.2.22. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

OpenClaw is an open-source messaging framework that allows developers to create custom messaging channels. One of its optional plugins, BlueBubbles, enhances direct messaging capabilities. However, a configuration-sensitive access-control issue has been identified in the BlueBubbles plugin, which can lead to unauthorized access under certain conditions.

Vulnerability Detail

The vulnerability arises from a mismatch in the access control mechanism when the 'allowFrom' configuration is empty or unset. In such cases, the BlueBubbles DM policy defaults to 'pairing', allowing unknown senders to bypass intended restrictions. This could lead to unauthorized direct messages being sent to users, especially in setups where the BlueBubbles account identifier is publicly reachable. The technical details reveal that the function responsible for sender authorization incorrectly returns true for empty allowlists, compromising the intended security model.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.22

This is the first release that contains the fix.

npm install openclaw@2026.2.22

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, ensure that the 'allowFrom' configuration is explicitly set to a non-empty value to prevent unauthorized access until the package is updated. For example, you can modify your configuration as follows: allowFrom: ['your-allowed-sender@example.com']

Conclusion

The OpenClaw BlueBubbles plugin vulnerability presents a moderate risk due to a pairing/allowlist mismatch when the 'allowFrom' configuration is empty. Users are advised to update to the patched version to secure their messaging environment and prevent unauthorized access.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability has a CVSS score of 5.3, indicating a moderate level of risk.

Users of the OpenClaw package, specifically those utilizing the BlueBubbles plugin with an empty 'allowFrom' configuration, are affected.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.

As a temporary measure, ensure that the 'allowFrom' configuration is set to a non-empty value to mitigate the risk of unauthorized access.

If exploited, unauthorized users may send direct messages to users, leading to privacy concerns and potential misuse of the messaging platform.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.22

This is the first release that contains the fix.

npm install openclaw@2026.2.22

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback