OpenClaw Vulnerability: Node Camera URL Payload Host-Binding Bypass

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
5.5

GHSA-2858-xg23-26fp: OpenClaw: Node camera URL payload host-binding bypass allowed gateway fetch pivots. Affects openclaw versions >= 2026.2.13, < 2026.3.2. Fixed in 2026.3.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

OpenClaw is an open-source package designed for managing camera functionalities in a networked environment. It allows users to capture snapshots and clips from connected cameras. The package operates under a trust model where paired nodes are considered to be within the same operator trust boundary. However, this model can be exploited due to a vulnerability that allows URL payloads to be fetched without proper host binding, potentially leading to security risks.

Vulnerability Detail

The vulnerability in OpenClaw arises from its handling of camera.snap and camera.clip node payload URL fields. The package accepts these URLs and downloads content directly on the gateway or agent host without ensuring that the downloads are bound to the resolved node host. This oversight allows a malicious or compromised paired node to redirect fetch requests to off-node destinations, which could lead to internal network probing or unauthorized data access. The technical flow involves fetching URL payloads directly in the writeUrlToFile function without validating the host, making it susceptible to Server-Side Request Forgery (SSRF) attacks.

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

This is the first release that contains the fix.

npm install openclaw@2026.3.2

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. It is strongly recommended to update to the patched version to mitigate the risk.

Conclusion

The OpenClaw vulnerability allows for URL payload host-binding bypass, which can lead to serious security risks if exploited by a malicious node. Users are urged to update to the latest patched version to safeguard their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 5.5, indicating a moderate level of risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

A compromised paired node could redirect fetch requests to unauthorized destinations, leading to potential data breaches or internal network probing.

While no specific workarounds are provided, it is advisable to monitor your network for unusual activity and plan to update to the patched version as soon as possible.

Yes, the vulnerability affects OpenClaw versions 2026.2.13 to 2026.3.1. Users should upgrade to version 2026.3.2 or later.

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

This is the first release that contains the fix.

npm install openclaw@2026.3.2

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.