OpenClaw: Trusted retry endpoint checks could match hostname prefixes
Affects openclawSource GCVE Database
CVSS 7.1 High : upgrade to 2026.5.7 soon.
Data as of 2 Jul 2026, 23:18 UTC
- Patch
- Available – fixed in 2026.5.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NWhat to do
Upgrade openclaw to 2026.5.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmopenclaw | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenClaw version 2026.5.7. Until patched, operators should pin retry endpoints to exact trusted origins to prevent hostname prefix matching issues. Additional mitigations include keeping channel and tool allowlists narrow, avoiding sharing a Gateway between mutually untrusted users, and disabling the affected retry endpoint feature when not needed.
Description
OpenClaw versions prior to 2026.5.7 have a vulnerability where trusted retry endpoint checks may incorrectly validate URLs by matching hostname prefixes rather than exact hostnames. This can allow lower-trust input to specify a retry endpoint URL that appears to be trusted but actually directs authentication material to an unintended external endpoint. The vulnerability affects the retry endpoint feature when enabled and reachable. The issue is mitigated by pinning retry endpoints to exact trusted origins and restricting access until the patched version is deployed.