CVE-2026-53839: Openclaw Auth Bypass Vulnerability

CVE-2026-53839 Overview

CVE-2026-53839 is a hostname validation flaw in OpenClaw versions before 2026.5.7. The vulnerability exists in retry endpoint checks that perform prefix matching rather than exact hostname matching. Attackers can register or control a hostname whose prefix resembles a trusted host. When OpenClaw retries a request, it accepts the attacker-controlled endpoint as trusted and forwards authentication material to it. The issue is tracked under CWE-1023 (Incomplete Comparison with Missing Factors) and affects the Node.js distribution of openclaw:openclaw.

Critical Impact
Authentication credentials and tokens can be exfiltrated to untrusted endpoints whose hostnames share a prefix with a trusted host.

Affected Products

OpenClaw openclaw versions prior to 2026.5.7
Node.js distribution of OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*)
Applications that depend on OpenClaw for outbound retry logic with authentication

Discovery Timeline

2026-06-12 - CVE-2026-53839 published to NVD
2026-06-17 - Last updated in NVD database

Technical Details for CVE-2026-53839

Vulnerability Analysis

OpenClaw retries failed outbound requests and validates the target hostname before resending authentication material. The validation compares the retry endpoint hostname against a trusted hostname using prefix matching. Any host whose name begins with the trusted hostname string passes the check. An attacker who controls a domain such as trusted-host.attacker.tld can satisfy the prefix check when trusted-host is the legitimate target. OpenClaw then transmits bearer tokens, cookies, or other authentication headers to the attacker-controlled endpoint during retry. The flaw requires low privileges and network access, and exploitation does not require user interaction.

Root Cause

The root cause is incomplete string comparison logic in the retry endpoint validation routine. The implementation uses a prefix or startsWith-style comparison instead of an exact equality check or a parsed-host comparison anchored on the full hostname and domain boundary. This category of weakness is captured by CWE-1023, where a comparison omits a factor required for security, in this case the trailing domain boundary.

Attack Vector

Exploitation is network-based. An attacker provisions a hostname whose label begins with the trusted hostname string used by OpenClaw. The attacker influences the retry destination so that OpenClaw issues a request to the attacker-controlled host. Because the prefix check succeeds, OpenClaw treats the destination as trusted and includes authentication material in the retry request. The attacker captures the credentials and can reuse them against the legitimate service.

No verified public proof-of-concept code is available. Refer to the Vulncheck Advisory on OpenClaw for technical details on the matching logic.

Detection Methods for CVE-2026-53839

Indicators of Compromise

Outbound HTTP requests from OpenClaw-enabled applications to hostnames that share a leading label with known trusted endpoints but resolve to unfamiliar IP addresses
Authentication headers, bearer tokens, or session cookies appearing in traffic to non-production domains during retry sequences
DNS resolutions for newly registered domains whose first label matches an internal or partner hostname

Detection Strategies

Inventory all services using OpenClaw and confirm package versions against 2026.5.7 or later
Inspect application logs for retry events that target hostnames not on an approved allowlist
Correlate outbound TLS Server Name Indication (SNI) values with the configured trusted retry endpoints

Monitoring Recommendations

Forward proxy and DNS logs to a centralized analytics platform and alert on lookalike hostnames that begin with sensitive service names
Monitor egress traffic for authentication headers sent to unexpected destinations
Track package manifests in CI/CD pipelines to flag OpenClaw versions below 2026.5.7

How to Mitigate CVE-2026-53839

Immediate Actions Required

Upgrade OpenClaw to version 2026.5.7 or later across all Node.js services
Rotate any credentials, API keys, or tokens that OpenClaw may have transmitted during retry operations
Audit retry endpoint configurations and remove any wildcard or prefix-based trust entries

Patch Information

The maintainers released a fix in OpenClaw 2026.5.7. The advisory and patch details are published in the OpenClaw GitHub Security Advisory GHSA-77q5-rr5v-x43q. The fix replaces prefix-based hostname matching with exact hostname comparison in the retry endpoint validation path.

Workarounds

Restrict outbound network access from OpenClaw services to an explicit allowlist of trusted hostnames at the egress proxy or firewall layer
Disable retry behavior for requests that carry authentication material until the upgrade is applied
Implement DNS filtering to block resolution of newly registered domains that resemble internal hostnames

bash

# Upgrade OpenClaw to the patched version
npm install openclaw@2026.5.7 --save
npm ls openclaw