Auth Bypass Vulnerability in OpenClaw Package via Encoded Paths

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
6.9

GHSA-v865-p3gq-hw6m: OpenClaw has encoded-path auth bypass in plugin /api/channels route classification. Affects openclaw versions < 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 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 package designed for managing and interacting with channels through a RESTful API. It allows developers to create, manage, and utilize channels effectively. However, certain versions of OpenClaw are vulnerable to an authentication bypass issue that can be exploited through encoded path requests, particularly in the '/api/channels' route.

Vulnerability Detail

The vulnerability arises from a canonicalization depth mismatch in the authentication checks for plugin routes. Specifically, deeply encoded slashes (e.g., multi-encoded '%2f') can bypass the intended authentication checks, allowing unauthorized access to protected resources. This issue can lead to significant security risks, as it allows attackers to exploit the API without proper authentication, potentially exposing sensitive data or functionality.

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

As a temporary workaround, you can implement additional validation on incoming requests to ensure that the paths are not deeply encoded or malformed. This can be done by adding a middleware function that checks the request path before it reaches the route handlers.

Conclusion

The OpenClaw package has a significant vulnerability that allows for authentication bypass through encoded paths. It is crucial for users of this package to update to version 2026.3.2 or later to ensure their applications are secure. Additionally, 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 is an authentication bypass that allows unauthorized access to the '/api/channels' route through encoded path requests.

Versions of OpenClaw up to and including 2026.3.1 are affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

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

If an immediate update is not possible, consider implementing additional request validation as a temporary workaround 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.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.