Elevated Scope Acceptance in OpenClaw's Trusted-Proxy Control UI

openclaw Updated 02 Jul 2026

Summary

02/07/2026
HIGH
Yes i
High
8.8

GHSA-qjpc-qf9m-xwmr: OpenClaw: Trusted-proxy Control UI WebSocket accepted client-declared scopes before pairing. Affects openclaw versions < 2026.5.18. Fixed in 2026.5.18. 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 software package designed for managing and controlling gateway operations through a user-friendly interface. It supports various authentication modes, including trusted-proxy, which allows for secure communication between clients and servers. However, a vulnerability exists in the trusted-proxy Control UI mode that permits unauthorized scope elevation, potentially compromising system integrity.

Vulnerability Detail

In trusted-proxy Control UI mode, OpenClaw improperly accepts a WebSocket client's declared operator scopes before those scopes are validated against a server-approved pairing or trusted-proxy authorization baseline. This flaw allows an unpaired or restricted trusted-proxy Control UI client to gain cached 'operator.admin' authority on its WebSocket connection, enabling unauthorized access to admin-gated Gateway RPCs until the connection is terminated or revalidated. The vulnerability is classified with a CVSS score of 8.8, indicating a high severity level.

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

This is the first release that contains the fix.

npm install openclaw@2026.5.18

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

Workaround

Before upgrading, ensure that trusted-proxy Control UI access is limited to users who should have the requested scopes. This can be done by adjusting the authorization settings in your configuration file.

Conclusion

The vulnerability in OpenClaw's trusted-proxy Control UI mode poses a significant risk by allowing unauthorized scope elevation. It is crucial for users to upgrade to the patched version and implement necessary access restrictions to safeguard their systems.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows unauthorized clients to declare elevated scopes in the trusted-proxy Control UI mode, potentially granting them admin access.

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

It is recommended to upgrade to version 2026.5.18 or later to mitigate the vulnerability.

Failure to address this vulnerability could lead to unauthorized access to sensitive administrative functions, compromising the security of your gateway operations.

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

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

This is the first release that contains the fix.

npm install openclaw@2026.5.18

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