DNS Rebinding Vulnerability in OpenClaw: SSRF Hostname Validation Bypass

openclaw Updated 18 Apr 2026

Summary

17/04/2026
MODERATE
Yes i
Moderate
6.3

GHSA-xq94-r468-qwgj: OpenClaw: Browser SSRF hostname validation could be bypassed by DNS rebinding. Affects openclaw versions < 2026.4.10. Fixed in 2026.4.10. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OpenClaw is an open-source package available on npm that facilitates browser-based interactions and navigation. It is designed to enhance web applications by providing a structured way to handle browser requests. However, it has been found to be vulnerable to a DNS rebinding attack, which can allow malicious actors to bypass hostname validation, leading to potential Server-Side Request Forgery (SSRF) exploits.

Vulnerability Detail

The vulnerability arises from inadequate hostname validation in OpenClaw, which can be exploited through DNS rebinding techniques. This allows an attacker to manipulate DNS responses to redirect requests to unauthorized servers, potentially leading to data leakage or unauthorized actions on behalf of the user. The flaw is particularly concerning as it undermines the browser's navigation policy, which is supposed to ensure that requests are only made to allowed hosts. The technical fix involves tightening the hostname validation process to ensure that only whitelisted URLs are accepted, preventing unauthorized access.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.10

This is the first release that contains the fix.

npm install openclaw@2026.4.10

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to update to the patched version as soon as possible.

Conclusion

The OpenClaw package is vulnerable to a DNS rebinding attack that can compromise hostname validation, leading to potential SSRF exploits. Users are strongly advised to upgrade to version 2026.4.10 or newer to secure their applications against this vulnerability. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows DNS rebinding attacks that can bypass hostname validation, leading to potential SSRF exploits.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in open-source packages. Visit Vulert Scanner to analyze your package-lock.json.

While there are no specific workarounds, it is crucial to prioritize updating to the patched version to mitigate risks.

The CVSS score for this vulnerability is 6.3, indicating a moderate level of severity.

The vulnerability was reported by @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.10

This is the first release that contains the fix.

npm install openclaw@2026.4.10

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback