OpenClaw Canvas Authentication Bypass Vulnerability - High Risk IP-Based Exploit

openclaw Updated 04 Mar 2026

Summary

04/03/2026
HIGH
Yes i
High
7.4

GHSA-vvjh-f6p9-5vcf: OpenClaw Canvas Authentication Bypass Vulnerability. Affects openclaw versions < 2026.2.19. Fixed in 2026.2.19. 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 Your last release was probably never penetration tested 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 gateway designed for seamless integration of various applications, providing a canvas for user interactions. It enables WebSocket connections and HTTP requests for real-time data exchange. However, a critical vulnerability has been identified in its authentication mechanism, specifically affecting versions up to 2026.2.17, where IP-based authentication can be exploited, allowing unauthorized access to sensitive endpoints.

Vulnerability Detail

The vulnerability arises from the authorizeCanvasRequest() function in OpenClaw, which implements an IP-based fallback for authentication. When a WebSocket client authenticates from a private IP address, all subsequent HTTP requests from that same IP are granted access without requiring their own authentication tokens. This flaw can be exploited in environments where multiple clients share a single IP address, such as corporate NATs or containerized deployments, allowing an unauthenticated attacker to gain full access to canvas endpoints by simply sharing an IP with a legitimate client.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.19

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

Workaround

As a temporary workaround, consider implementing network segmentation to prevent multiple clients from sharing the same IP address. Additionally, you can restrict access to the OpenClaw gateway by configuring firewall rules to limit exposure to trusted IPs only.

Conclusion

The OpenClaw Canvas Authentication Bypass Vulnerability poses a significant risk due to its IP-based authentication flaw, allowing unauthorized access to sensitive endpoints. It is crucial to update to the patched version to protect against potential exploits. Utilizing tools like Vulert can aid in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 7.4, indicating a high severity level.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

The vulnerability allows unauthorized access to sensitive canvas endpoints, potentially leading to information disclosure and unauthorized actions within the application.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

If immediate updating is not possible, implement network segmentation and restrict access to trusted IPs as a temporary measure to mitigate the risk.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.19

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