Policy Enforcement Bypass in OpenClaw via Zalo Display Name

Compliance Impact

The vulnerability allows attackers to manipulate display names to receive agent responses intended for other Zalo identities, potentially leading to unauthorized access to sensitive information.

Such unauthorized access and data exposure could impact compliance with data protection regulations like GDPR and HIPAA, which require strict controls on personal data confidentiality and access.

However, the advisory notes that OpenClaw's trusted-operator model remains intact unless separate security boundaries are crossed, implying that the risk is limited to scenarios where the vulnerable feature is enabled and accessible.

Mitigations such as using stable identifiers, restricting friend access, and disabling the affected feature when unnecessary can help reduce compliance risks.

Useful 0 Not Useful 0

Executive Summary

This vulnerability affects OpenClaw versions before 2026.5.3 and involves a policy enforcement flaw in the Zalo allowFrom feature.

Zalo contacts have mutable display metadata, meaning their display names can be changed. Due to this, the allowFrom policy entries can be matched incorrectly when display names are altered.

Attackers who can change their display names could exploit this flaw to receive agent responses intended for different Zalo identities, effectively bypassing authentication controls.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to an authentication bypass through spoofing, allowing attackers to impersonate other Zalo identities by manipulating display names.

As a result, attackers could receive sensitive agent responses or information meant for other users, potentially exposing confidential data.

This could undermine trust in communications and lead to unauthorized access to information within systems using OpenClaw with the affected feature enabled.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate the vulnerability in OpenClaw before version 2026.5.3, you should take the following immediate steps:

• Upgrade OpenClaw to version 2026.5.3 or later, where the vulnerability is patched.
• Use stable Zalo identifiers instead of mutable display names to avoid spoofing.
• Restrict friend access and keep allowlists narrow to limit exposure.
• Avoid sharing Gateways between untrusted users.
• Disable the affected allowFrom feature when it is not necessary.

Useful 0 Not Useful 0