Is CVE-2026-53807 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53807 being exploited in the wild.

How severe is CVE-2026-53807?

High severity, with a CVSS score of 8.8, published 11 June 2026.

Which products and versions are affected?

openclaw (npm) SEMVER:introduced=0,fixed=2026.5.6; Openclaw < 2026.5.6.

Is there a fix for CVE-2026-53807?

Yes. openclaw (npm): upgrade to 2026.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53807 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53807?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53807: OpenClaw authorization bypass in Telegram interactive callbacks

Q: Is there a fix for CVE-2026-53807?

Yes. openclaw (npm): upgrade to 2026.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53807 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-53807?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53807 · Severity: high · CVSS 8.8 · Published 2026-06-11

OpenClaw, a tool used for managing Telegram bot interactions, contains a security flaw in how it validates user permissions. An authenticated user can bypass configured sender restrictions by using specific interactive callbacks, allowing them to execute commands they should not have access to. This could lead to unauthorized control over the bot's functions or access to sensitive operations. Users should update to version 2026.5.6 to resolve this issue.

Technologies: openclaw (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-53807 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53807 being exploited in the wild.
How severe is CVE-2026-53807?: High severity, with a CVSS score of 8.8, published 11 June 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.5.6; Openclaw < 2026.5.6.
Is there a fix for CVE-2026-53807?: Yes. openclaw (npm): upgrade to 2026.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53807 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53807?: Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openclaw (npm): upgrade to 2026.5.6 or later
```
npm install openclaw@2026.5.6
```

Technical details

An authorization bypass vulnerability (CWE-863) exists in OpenClaw's Telegram interactive callback handling. The root cause is a logic error where a user can invoke a callback that marks them as an authorized sender before the 'commands.allowFrom' allowlist validation is applied. This allows an authenticated attacker to bypass configured sender restrictions and trigger command behaviors. The vulnerability is reachable over the network and requires basic authentication (PR:L). A fix is available in version 2026.5.6.

Affected products

OpenClaw openclaw < 2026.5.6

Identifiers

CVE-2026-53807
GHSA-w5ww-7chg-mxcq

Timeline

2026-05-28: advisory: GitHub Security Advisory published
2026-06-11: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.