GitStock

openclaw/openclaw · Security

OpenClaw: Browser SSRF hostname validation could be bypassed by DNS rebinding

Open GitHub
GHSA ID
GHSA-xq94-r468-qwgj
CVE ID
CVE-2026-43582
Severity
medium
Published
Updated
CVSS
6.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
CVSS v3
6.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
CVSS v4
4.9 · CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

Description

Summary

Browser SSRF hostname validation could be bypassed by DNS rebinding.

Affected Packages / Versions

  • Package: openclaw
  • Ecosystem: npm
  • Affected versions: < 2026.4.10
  • Patched versions: >= 2026.4.10

Impact

Browser navigation policy could validate a hostname/IP resolution that differed from the address Chromium ultimately used, allowing DNS rebinding style SSRF pivots.

Technical Details

The fix tightens strict browser hostname navigation so unallowlisted hostname URLs fail closed under restrictive policy.

Fix

The issue was fixed in #64367. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.

Fix Commit(s)

  • 121c452d666d4749744dc2089287d0227aae2ed3
  • PR: #64367

Release Process Note

Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

CWEs

  • CWE-350 · Reliance on Reverse DNS Resolution for a Security-Critical Action
  • CWE-918 · Server-Side Request Forgery (SSRF)

References