CVE-2026-100574

OpenClaw before 2026.8.1 SSRF via Trusted-Host DNS

Published Sep 26, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
OpenClaw (npm package 'openclaw') before 2026.8.1 contains a server-side request forgery vulnerability in its trusted-host DNS checks. For fetches that use the trusted-host DNS recheck, a trusted hostname that resolves to an unspecified address (0.0.0.0 or ::) bypasses the SSRF destination validation. An attacker who can influence DNS for an allowed hostname can therefore cause a guarded fetch to reach a service bound only to loopback and disclose its response; the practical impact depends on the reachable service and the data it returns. Fixed in 2026.8.1.

Analysis

AI-generated

Technical impact

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.

Affected Systems

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

Risk and Exploitability

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the OpenClaw npm package to version 2026.8.1 or newer, which removes the vulnerable DNS handling code.
  • Add application‑level validation to reject fetch targets that resolve to 0.0.0.0, ::, or other loopback addresses and restrict outbound requests to a whitelist of approved public hosts.
  • Use firewalls or network isolation to block the application’s connections to loopback interfaces or internal services that should not be exposed to untrusted code paths.

Generated by OpenCVE AI on September 26, 2026 at 04:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description OpenClaw (npm package 'openclaw') before 2026.8.1 contains a server-side request forgery vulnerability in its trusted-host DNS checks. For fetches that use the trusted-host DNS recheck, a trusted hostname that resolves to an unspecified address (0.0.0.0 or ::) bypasses the SSRF destination validation. An attacker who can influence DNS for an allowed hostname can therefore cause a guarded fetch to reach a service bound only to loopback and disclose its response; the practical impact depends on the reachable service and the data it returns. Fixed in 2026.8.1.
Title OpenClaw before 2026.8.1 SSRF via Trusted-Host DNS
First Time appeared Openclaw
Openclaw openclaw
Weaknesses CWE-918
CPEs cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*
Vendors & Products Openclaw
Openclaw openclaw
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 29, 2026, 4:55 PM
Reserved
Sep 26, 2026, 1:03 AM
Status
Deferred
Published
Sep 26, 2026, 3:17 AM
Modified
Sep 29, 2026, 5:17 PM