Is CVE-2026-53857 exploited in the wild?

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

How severe is CVE-2026-53857?

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.3; Openclaw < 2026.5.3, <= 2026.5.2.

Is there a fix for CVE-2026-53857?

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

How is CVE-2026-53857 attacked?

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

Am I affected by CVE-2026-53857?

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-53857: OpenClaw policy enforcement bypass in Zalo allowFrom policy

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

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

Q: How is CVE-2026-53857 attacked?

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

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

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

OpenClaw, a gateway for managing Zalo communications, contains a flaw in how it identifies users. An attacker can change their display name to match a trusted user's name, potentially tricking the system into sending them messages or data intended for someone else. This could lead to unauthorized access to private communications or sensitive information.

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

Quick answers

Is CVE-2026-53857 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53857 being exploited in the wild.
How severe is CVE-2026-53857?: 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.3; Openclaw < 2026.5.3, <= 2026.5.2.
Is there a fix for CVE-2026-53857?: Yes. openclaw (npm): upgrade to 2026.5.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53857 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53857?: 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.3 or later
```
npm install openclaw@2026.5.3
```

Technical details

A vulnerability in OpenClaw's Zalo 'allowFrom' policy implementation allows for authentication bypass via spoofing (CWE-290). The root cause is the system's reliance on mutable display metadata rather than stable, unique identifiers when evaluating access policies. An attacker with a Zalo account can modify their display name to match a name listed in a policy entry, potentially receiving agent responses or data intended for a different identity. This requires the 'allowFrom' feature to be enabled and reachable. The issue is addressed in version 2026.5.3 by prioritizing stable identifiers.

Affected products

openclaw openclaw <= 2026.5.2

Identifiers

CVE-2026-53857
GHSA-8c59-hr4w-qg69

Timeline

2026-05-28: disclosed: Initial disclosure by reporter
2026-06-18: advisory: GitHub Advisory published
2026-05-28: patched: Version 2026.5.3 released

References

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