dbcve.org
OpenclawApplication

CVE-2026-8305

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 2026.2.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
A vulnerability was detected in OpenClaw up to 2026.1.24. The impacted element is the function handleBlueBubblesWebhookRequest of the file extensions/bluebubbles/src/monitor.ts of the component bluebubbles Webhook. Performing a manipulation results in improper authentication. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 2026.2.12 is sufficient to resolve this issue. The patch is named a6653be0265f1f02b9de46c06f52ea7c81a836e6. The affected component should be upgraded.

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 · high confidence

An improper authentication vulnerability exists in the handleBlueBubblesWebhookRequest function of the bluebubbles Webhook component in OpenClaw. This allows remote attackers to bypass authentication mechanisms. The vulnerability affects versions up to 2026.1.24.

MitigationUpgrade OpenClaw to version 2026.2.12 or later to apply the authentication fix. This is a critical (CVSS 9.8) vulnerability requiring immediate action.

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.2.12

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify OpenClay installation and version
    Locate the OpenClay installation directory and check the version file or binary version information. Common locations include /opt/openclaw, /usr/local/openclaw, or the application data directory. Run: openclaw --version or check package.json/version.txt in the installation root.
    Affected if The installed version is lower than 2026.2.12
  2. Confirm bluebubbles Webhook component is enabled
    Examine the OpenClay configuration files for the bluebubbles webhook feature. Look for settings like 'bluebubbles', 'webhook', or 'bluebubbles_webhook' in config.json, settings.json, or .env files within the OpenClay configuration directory.
    Affected if The bluebubbles webhook feature is explicitly enabled or configured in the OpenClay configuration
  3. Verify webhook endpoint is exposed
    Check the OpenClay server configuration or API routes to determine if the webhook endpoint is publicly accessible. Look for routes matching /webhook/bluebubbles or similar patterns in the server configuration files.
    Affected if The webhook endpoint is exposed and reachable from external networks
  4. Inspect the monitor.ts source file for the vulnerability
    If source code is available, examine extensions/bluebubbles/src/monitor.ts and locate the handleBlueBubblesWebhookRequest function. Check for missing authentication validation or credential checks within this function.
    Affected if The handleBlueBubblesWebhookRequest function lacks proper authentication validation logic

You are affected if OpenClay version is below 2026.2.12 AND the bluebubbles webhook component is enabled and accessible.

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.2.12 or later
Fixed in 2026.2.12
Vendor patch github.com →
Interim mitigation

Upgrade OpenClaw to version 2026.2.12 or later to apply the authentication fix. This is a critical (CVSS 9.8) vulnerability requiring immediate action.

Recommended fix High confidence

2026.2.12

  1. Ensure you have a backup of your current OpenClaw installation and data
  2. Locate your current OpenClaw installation directory
  3. Check your current version to confirm it is below 2026.2.12
  4. Download OpenClaw version 2026.2.12 from the official repository or release channel
  5. Stop any running OpenClaw services or processes
  6. Install version 2026.2.12, replacing the previous installation
  7. Verify the installation was successful by checking the version
  8. Restart OpenClaw services

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8305 — 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-8305 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