Which versions of OpenClaw are affected by CVE-2026-53807?

OpenClaw prior to version 2026.5.6 contains an authorization bypass vulnerability (CVSS 7.7) that allows authenticated Telegram users to execute restricted commands by circumventing the configured…. A patch is available.

How to fix or mitigate CVE-2026-53807?

Within 24 hours: Audit current OpenClaw deployment versions and Telegram command allowlist configurations. Within 7 days: Apply vendor patch to upgrade all OpenClaw instances to version 2026.5.6 or later. Within 30 days: Validate that commands.allowFrom sender allowlist is functioning correctly and re-test command execution restrictions with authorized and unauthorized Telegram sender accounts.

OpenClaw CVE-2026-53807

Q: What is the CVSS score of CVE-2026-53807?

CVE-2026-53807 has a CVSS 4.0 base score of 7.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-36313 HIGH

Incorrect Authorization (CWE-863)

2026-06-11 VulnCheck

GHSA-5chm-94mp-c9cg

Authentication Bypass Openclaw

7.7

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.5 HIGH

Network-reachable via Telegram (AV:N) but requires a specific callback-ordering trick (AC:H); attacker must be an authenticated Telegram user (PR:L) and gains full command-execution impact.

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

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jun 11, 2026 - 21:26 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.5.6.

DescriptionCVE.org

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.

AnalysisAI

Authorization bypass in OpenClaw prior to 2026.5.6 allows authenticated Telegram users to circumvent the commands.allowFrom sender allowlist by invoking interactive callbacks that mark the caller as authorized before validation runs. Reported by VulnCheck with a vendor patch available, this CWE-863 flaw lets attackers execute restricted command behaviors outside configured Telegram sender restrictions, though no public exploit identified at time of analysis.

Technical ContextAI

OpenClaw integrates with Telegram and exposes interactive callback handlers tied to bot commands. The commands.allowFrom configuration is intended to restrict which Telegram sender IDs may invoke commands, but the callback processing path applies an authorization side effect (marking the user as an authorized sender) before consulting the allowlist. This is a textbook CWE-863 Incorrect Authorization issue: the access decision is made in the wrong order relative to state that the attacker controls, so the check is effectively self-attesting. CPE coverage targets cpe:2.3:a:openclaw:openclaw across all versions up to the fixed release.

RemediationAI

Upgrade OpenClaw to version 2026.5.6 or later, which is the vendor-released patch referenced in GHSA-w5ww-7chg-mxcq (https://github.com/openclaw/openclaw/security/advisories/GHSA-w5ww-7chg-mxcq). If immediate patching is not possible, restrict access to the Telegram bot by reducing the bot's exposure (for example, move the bot to a private group whose membership is itself the trust boundary, or rotate the bot token and limit who knows it) so that arbitrary authenticated Telegram users cannot reach the callback handlers; note this loses the convenience of public/invitational use. Audit recent Telegram command activity for senders not present in commands.allowFrom and consider temporarily disabling sensitive interactive callbacks until the upgrade is applied, accepting the loss of those bot features in exchange for a closed bypass path.