OpenClaw implements a trusted‑host DNS check when performing outgoing fetches. The check incorrectly accepts a hostname that resolves to 0.0.0.0 or ::, allowing a server‑side request forgery. When an attacker can influence the DNS record for an allowed hostname, the application can be forced to connect to a service bound only to the loopback interface and reveal its response. The practical impact depends on the internal service accessed and the data it returns, potentially exposing sensitive internal information or service functionality.

The vulnerability affects the OpenClaw npm package (named "openclaw"). Versions earlier than 2026.8.1 are impacted. No other vendors or products are affected.

The CVSS score of 8.2 indicates a high severity issue. EPSS information is not available, and the vulnerability is not listed in CISA’s KEV catalog. The attack vector is a server‑side request forgery that requires the attacker to manipulate DNS entries for a hostname included in the package’s trusted‑host list. The exploitation succeeds only if the application performs a fetch with the trusted‑host DNS recheck enabled; therefore any deployment that accepts user‑controlled DNS or allows modification of the trusted‑host list is vulnerable.