Unauthorized Access to Gateway Control UI Configuration in OpenClaw

openclaw Updated 05 May 2026

Summary

04/05/2026
MODERATE
Yes i
Moderate
6.9

GHSA-93rg-2xm5-2p9v: OpenClaw's Gateway Control UI bootstrap config required Gateway auth. Affects openclaw versions < 2026.4.22. Fixed in 2026.4.22. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

OpenClaw is an open-source project that provides a Gateway Control UI for managing and configuring gateways. It allows users to interact with various gateway functionalities through a web interface. The package is designed to ensure secure access to sensitive configurations, but a recent vulnerability has been identified that compromises this security.

Vulnerability Detail

The vulnerability arises from the Gateway Control UI bootstrap configuration endpoint, which was accessible without proper authentication even when Gateway authentication was enabled. This flaw could allow unauthorized users to read sensitive configuration fields that are meant to be protected, potentially leading to exposure of critical information and unauthorized access to the Control UI.

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

This is the first release that contains the fix.

npm install openclaw@2026.4.22

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

Workaround

As a temporary workaround, ensure that Gateway authentication is enabled and restrict access to the Control UI until the package is updated. Regularly monitor access logs for any unauthorized attempts.

Conclusion

In summary, the OpenClaw package has a vulnerability that allows unauthorized access to sensitive configuration data in the Gateway Control UI. It is crucial to update to version 2026.4.22 to mitigate this risk. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows unauthorized access to sensitive configuration data in the Gateway Control UI.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in real-time. Visit Vulert Scanner for a quick assessment.

The risks include exposure of sensitive configuration data and potential unauthorized access to the Control UI, which could lead to further security breaches.

Yes, a patch is available in version 2026.4.22 of the OpenClaw package. It is recommended to update to this version.

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

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

This is the first release that contains the fix.

npm install openclaw@2026.4.22

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.