Skip to main content
VulnerabilityPublished Updated

CVE-2026-53857: OpenClaw · Zalo allowFrom could bind to mutable display names

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 2026.5.4 soon.

Data as of 17 Nov 2026, 19:05 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.5.4.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.5.4
Fixed in
  • 2026.5.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available starting with OpenClaw version 2026.5.3 and should be applied promptly. Until patched, operators should use stable Zalo identifiers rather than mutable display names, restrict friend access, keep channel and tool allowlists narrow, avoid sharing Gateways between mutually untrusted users, and disable the affected feature if it is not needed.

Description

A vulnerability in OpenClaw's Zalo allowFrom feature allows binding to mutable display names, potentially causing agent responses to be misdirected to another Zalo identity. This affects versions from 2026.1.29 up to but not including 2026.5.4. The issue depends on operator configuration and the trust level of inputs reaching the affected feature. A fix is available starting with version 2026.5.3. Mitigations include using stable Zalo identifiers, restricting friend access, narrowing allowlists, avoiding shared Gateways between untrusted users, and disabling the feature if not needed.

References

Community reviews

Loading reviews…