Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-100574 – SSRF (Trusted-Host DNS Bypass) – OpenClaw before 2026.8.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100574 is a server-side request forgery (SSRF) vulnerability in OpenClaw (npm package openclaw) affecting all versions prior to 2026.8.1. The flaw lies in OpenClaw’s "trusted-host DNS recheck" logic, which is meant to validate that a fetch destination resolves to a safe address before allowing the request to proceed. The issue carries a CVSS v4.0 base score of 8.2 (High).

Technical details

  • Root cause: When OpenClaw performs a guarded fetch to a hostname on its trusted-host allowlist, it re-resolves the hostname’s DNS and checks the resulting address against SSRF destination restrictions. This recheck fails to properly reject DNS answers of 0.0.0.0 or :: (the unspecified/"any" addresses).
  • Trigger conditions: An attacker who can influence DNS resolution for a hostname that OpenClaw treats as "trusted" (for example, by controlling the authoritative DNS for that hostname, or otherwise poisoning/spoofing the resolution) can cause the hostname to resolve to 0.0.0.0 or ::.
  • Attack vector: Network — no authentication and no user interaction are required, but the attacker must be able to influence DNS resolution for an allowed hostname, which adds attack complexity.
  • Impact: The unspecified-address resolution bypasses OpenClaw’s SSRF destination validation, allowing the guarded fetch to instead reach a service bound only to loopback (localhost) on the host running OpenClaw. This can disclose the response of that internal service; the practical impact depends on which loopback-bound service is reachable and what data it returns. Confidentiality impact is high; there is no integrity or availability impact.

Affected software

  • openclaw (npm package), all versions prior to 2026.8.1
  • Fixed in version 2026.8.1 and later

Severity

  • CVSS v4.0 Base Score: 8.2 (High) — 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
  • CVSS v3.1 Base Score (alternate scoring): 5.9 (Medium) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade openclaw to version 2026.8.1 or later, which corrects the trusted-host DNS recheck to reject unspecified addresses (0.0.0.0/::).
  • If no patch can be applied immediately: Avoid adding hostnames to OpenClaw’s trusted-host allowlist unless their DNS is fully under your own operational control, since the vulnerability requires an attacker to influence DNS resolution for an allowed hostname. Where possible, restrict or monitor egress from the OpenClaw host to loopback-bound services, and audit which internal services are reachable via loopback on hosts running OpenClaw.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge