GHSA-77q5-rr5v-x43q: OpenClaw: Trusted retry endpoint checks could match hostname prefixes
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.
AI Analysis
Technical Summary
OpenClaw's trusted retry endpoint validation logic could match hostname prefixes instead of exact hostnames, allowing a retry endpoint URL chosen by lower-trust input to pass validation improperly. This flaw could cause authentication material to be sent to endpoints outside the intended trusted targets. The vulnerability does not alter the overall trusted-operator model of OpenClaw but impacts the specific retry endpoint feature when enabled. The first stable patched version addressing this issue is 2026.5.7.
Potential Impact
If the affected retry endpoint feature is enabled and accessible, an attacker controlling lower-trust input could cause authentication credentials or material to be sent to an endpoint outside the intended trusted set. The practical impact depends on the operator's configuration and whether untrusted input can reach the retry endpoint selection path. This could lead to unauthorized disclosure of authentication material.
Mitigation Recommendations
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.
GHSA-77q5-rr5v-x43q: OpenClaw: Trusted retry endpoint checks could match hostname prefixes
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.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenClaw's trusted retry endpoint validation logic could match hostname prefixes instead of exact hostnames, allowing a retry endpoint URL chosen by lower-trust input to pass validation improperly. This flaw could cause authentication material to be sent to endpoints outside the intended trusted targets. The vulnerability does not alter the overall trusted-operator model of OpenClaw but impacts the specific retry endpoint feature when enabled. The first stable patched version addressing this issue is 2026.5.7.
Potential Impact
If the affected retry endpoint feature is enabled and accessible, an attacker controlling lower-trust input could cause authentication credentials or material to be sent to an endpoint outside the intended trusted set. The practical impact depends on the operator's configuration and whether untrusted input can reach the retry endpoint selection path. This could lead to unauthorized disclosure of authentication material.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-77q5-rr5v-x43q
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a46ecc527e9c7971943d82b
Added to database: 07/02/2026, 22:57:09 UTC
Last enriched: 07/02/2026, 23:18:12 UTC
Last updated: 07/03/2026, 03:36:13 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.