dbcve.org
OpenclawApplication

CVE-2026-53860

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.5.7 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenClaw before 2026.5.7 contains a sender policy bypass vulnerability in BlueBubbles that allows participants to match allowlist entries through conversation metadata rather than stable sender identity. Attackers can influence conversation-level identifiers to receive agent responses intended for configured senders, potentially bypassing access controls.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OpenClaw's BlueBubbles component before version 2026.5.7 has a sender policy bypass where allowlist matching uses manipulable conversation metadata (e.g., conversation identifiers) instead of verifying stable sender identity. Attackers can influence conversation-level identifiers to receive agent responses intended for configured allowlisted senders, bypassing access controls.

MitigationUpgrade to OpenClaw version 2026.5.7 or later, which implements stable sender identity verification for allowlist matching instead of relying on conversation metadata.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.5.7= 2026.5.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed OpenClaw BlueBubbles version
    Run 'openclaw --version' or check the BlueBubbles component version through the application interface or package manager
    Affected if Version is less than 2026.5.7 or equals 2026.5.7
  2. Verify allowlist configuration exists
    Inspect the BlueBubbles configuration files (typically in /etc/openclaw/ or ~/.openclaw/) for any sender allowlist settings
    Affected if A sender allowlist is configured with specific conversation identifiers or metadata-based rules
  3. Confirm allowlist uses conversation metadata instead of stable sender identity
    Review the allowlist policy configuration to identify if matching relies on conversation identifiers, thread IDs, or similar metadata rather than verified sender identity attributes like cryptographic keys or stable user IDs
    Affected if Allowlist rules reference manipulable conversation identifiers or metadata rather than immutable sender identifiers
  4. Check for incoming message routing to allowlisted senders
    Review message logs or audit trails to see if agent responses are being routed based on conversation-level metadata
    Affected if Responses are being delivered based on conversation metadata that could be influenced by external parties

User is affected if running OpenClaw BlueBubbles version 2026.5.7 or earlier with an active sender allowlist that relies on conversation metadata for matching rather than verified stable sender identity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.5.7 or later
Fixed in 2026.5.7
Interim mitigation

Upgrade to OpenClaw version 2026.5.7 or later, which implements stable sender identity verification for allowlist matching instead of relying on conversation metadata.

Recommended fix High confidence

OpenClaw 2026.5.7 or later

  1. 1. Identify all OpenClaw installations currently running versions prior to 2026.5.7 or exactly version 2026.5.7
  2. 2. Review the BlueBubbles integration configuration and sender allowlist policies
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Backup the current OpenClaw configuration and data
  5. 5. Upgrade OpenClaw to version 2026.5.7 or later
  6. 6. After upgrade, verify the BlueBubbles sender policy enforcement now uses stable sender identity rather than conversation metadata
  7. 7. Test that the allowlist correctly validates sender identity and rejects manipulated conversation-level identifiers
  8. 8. Monitor for any legitimate sender access issues and adjust if needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53860 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data