CVE-2026-53859: OpenClaw < 2026.5.26 - Hostname Validation Bypass via Trailing-Dot Inconsistency
Summary
Hostname checks could treat trailing-dot hosts inconsistently. In affected versions, a request path that accepts model- or workspace-derived URLs could present the same hostname with a trailing dot and avoid a blocklist comparison.
This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.
Impact
When the affected feature is enabled and reachable, this could reach a destination that the operator expected the hostname policy to block. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.
Patched Versions
The first stable patched version is 2026.5.26.
Mitigations
keep private-network and metadata destinations blocked at the proxy or network layer until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
Other sources
OpenClaw before 2026.5.26 contains a hostname validation vulnerability allowing attackers to bypass blocklist comparisons using trailing-dot notation in model or workspace-derived URLs. Attackers can exploit inconsistent hostname checks to reach destinations that operators intended to block through hostname policies.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/openclawto a version that resolves this vulnerability.Fixed in 2026.5.26 - Compensating control
Keep private-network and metadata destinations blocked at the proxy or network layer until patched.
- Compensating control
Keep channel and tool allowlists narrow.
- Compensating control
Avoid sharing one Gateway between mutually untrusted users.
- Compensating control
Disable the affected feature when it is not needed.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53859?
CVE-2026-53859 has a medium severity rating of 6.5.
How do I fix CVE-2026-53859?
To fix CVE-2026-53859, upgrade OpenClaw to version 2026.5.26 or later.
What type of vulnerability is CVE-2026-53859?
CVE-2026-53859 is a hostname validation vulnerability that allows bypassing blocklist comparisons.
What are the potential impacts of exploiting CVE-2026-53859?
Exploitation of CVE-2026-53859 could allow attackers to access destinations that should be blocked by the server.
Can CVE-2026-53859 be exploited remotely?
Yes, CVE-2026-53859 can be exploited remotely due to its nature as a SSRF vulnerability.