Is CVE-2026-53849 exploited in the wild?

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

How severe is CVE-2026-53849?

High severity, with a CVSS score of 8.1, published 16 June 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-53849?

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

How is CVE-2026-53849 attacked?

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

Am I affected by CVE-2026-53849?

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-53849: OpenClaw privilege escalation in allowFrom feature

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

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

Q: How is CVE-2026-53849 attacked?

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

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

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-53849 · Severity: high · CVSS 8.1 · Published 2026-06-16

OpenClaw, a tool used for managing Discord-based automation and gateways, contains a security flaw in how it identifies users. An attacker can change their Discord display name to match a name on an authorized list, potentially gaining unauthorized access to tools or data intended for another user. This could lead to unauthorized actions being performed through the Discord gateway.

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

Quick answers

Is CVE-2026-53849 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53849 being exploited in the wild.
How severe is CVE-2026-53849?: High severity, with a CVSS score of 8.1, published 16 June 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.5.7; Openclaw < 2026.5.7, <= 2026.5.6.
Is there a fix for CVE-2026-53849?: Yes. openclaw (npm): upgrade to 2026.5.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53849 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53849?: 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.7 or later
```
npm install openclaw@2026.5.7
```

Technical details

OpenClaw versions up to 2026.5.6 are vulnerable to an authentication bypass (CWE-290) because the 'allowFrom' policy feature can be configured to match against Discord display names or global names. Since these metadata fields are mutable and can be changed by any Discord user, an attacker with low privileges can change their display name to match a trusted entry in the allowlist. This allows the attacker to assume the identity of a trusted user and gain agent access. The vulnerability is remediated in version 2026.5.7 by ensuring policies use stable Discord user IDs instead of mutable names.

Affected products

openclaw openclaw <= 2026.5.6

Identifiers

CVE-2026-53849
GHSA-cw4q-gqg5-g38h

Timeline

2026-05-28: disclosed
2026-06-18: advisory: GitHub Advisory published

References

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