IPv6 Multicast SSRF Classifier Bypass in OpenClaw

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
6.3

GHSA-h97f-6pqj-q452: OpenClaw has a IPv6 multicast SSRF classifier bypass. Affects openclaw versions < 2026.2.25. Fixed in 2026.2.25. 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 library designed for network fetching and navigation, primarily utilizing HTTP and HTTPS protocols. It is widely used in applications that require secure and efficient data retrieval from web resources. However, a recent vulnerability has been identified in its SSRF (Server-Side Request Forgery) IP classifier, which could potentially allow unauthorized access to internal resources.

Vulnerability Detail

The vulnerability arises from OpenClaw's failure to classify IPv6 multicast literals (specifically the range ff00::/8) as blocked or private-internal addresses. This oversight allows these multicast addresses to bypass SSRF preflight checks, potentially leading to unauthorized network requests. The technical details reveal that addresses such as ff02::1 and ff05::1:3 were not adequately classified, exposing the application to low-severity SSRF attacks. This issue has been categorized under CWE-918, indicating a weakness in the application's ability to validate and restrict network requests appropriately.

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.2.25

This is the first release that contains the fix.

npm install openclaw@2026.2.25

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

Workaround

As a temporary workaround, users can implement additional validation checks in their application to filter out IPv6 multicast addresses before making network requests. This can be done by adding a custom function to check if the IP address falls within the multicast range.

Conclusion

In summary, the IPv6 multicast SSRF classifier bypass in OpenClaw presents a moderate risk to applications utilizing this library. It is crucial for developers to update to the latest patched version to mitigate this vulnerability. Additionally, implementing temporary workarounds can help secure applications until the update is applied.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

Server-Side Request Forgery (SSRF) is a security vulnerability that allows an attacker to send unauthorized requests from a vulnerable server to internal or external resources.

If your application uses OpenClaw and does not update to the patched version, it may be susceptible to SSRF attacks, potentially exposing sensitive internal resources.

IPv6 multicast addresses are used to send data to multiple destinations simultaneously. They are identified by the prefix ff00::/8.

The vulnerability has been classified as moderate in severity, indicating that while it is not critical, it still poses a risk that should be addressed.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

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.2.25

This is the first release that contains the fix.

npm install openclaw@2026.2.25

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.