dbcve.org
OpenclawApplication

CVE-2026-53807

HIGH · 8.8 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 2026.5.6 or later.
See remediation →
94/100
Remediation priority · Urgent
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.6 contains an authorization bypass vulnerability in Telegram interactive callbacks that allows authenticated users to skip commands.allowFrom validation. Attackers can invoke affected callbacks to mark themselves as authorized senders before allowlist checks are applied, triggering command behavior outside configured Telegram sender restrictions.

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 before 2026.5.6 has an authorization bypass in Telegram interactive callbacks where the commands.allowFrom validation is not properly enforced. Authenticated users can invoke callbacks to self-authorize before allowlist checks execute, bypassing configured sender restrictions.

MitigationUpgrade to OpenClaw version 2026.5.6 or later which addresses the authorization validation order in Telegram callbacks.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed OpenClaw version
    Look for version file, package manifest, or run version command (e.g., openclaw --version, or inspect version.py, setup.py, pyproject.toml, or package.json in the installation directory)
    Affected if The installed version is below 2026.5.6
  2. Verify Telegram bot integration is enabled
    Inspect configuration files (e.g., config.yaml, config.json, .env) for Telegram bot token, bot settings, or telegram section. Check if the bot is actively running/registered.
    Affected if Telegram bot integration is configured and active
  3. Examine commands.allowFrom configuration
    Search configuration for 'allowFrom' directive under commands or Telegram callback settings. This may be in config files, database, or environment variables.
    Affected if commands.allowFrom is explicitly set to restrict senders (e.g., allowFrom: specific_users, allowFrom: whitelist)
  4. Review Telegram callback handler code
    Inspect the source code handling Telegram callback queries. Look for the validation order of authorization checks relative to self-authorization logic.
    Affected if The callback handler processes user self-authorization before checking the allowFrom restrictions (vulnerable code pattern)

You are affected if running OpenClaw below version 2026.5.6 with Telegram bot enabled and commands.allowFrom restrictions configured, where the callback handler allows self-authorization before allowFrom validation.

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.6 or later
Fixed in 2026.5.6
Interim mitigation

Upgrade to OpenClaw version 2026.5.6 or later which addresses the authorization validation order in Telegram callbacks.

Recommended fix Moderate confidence

OpenClaw 2026.5.6

  1. Identify the currently installed OpenClaw version in your deployment
  2. Backup your OpenClaw configuration files, database, and any custom scripts
  3. Upgrade OpenClaw to version 2026.5.6 or later by pulling the latest release from the official repository
  4. After upgrading, verify that the commands.allowFrom validation is now properly enforced on Telegram interactive callbacks
  5. Test that Telegram bot commands respect the sender allowlist configuration as intended
  6. Monitor logs to confirm the authorization bypass is no longer present

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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