Unauthorized Access Risk in OpenClaw: Browser Control Startup Vulnerability
Summary
GHSA-vpj2-69hf-rppw: OpenClaw: Browser control startup could continue unauthenticated after auth bootstrap failure. Affects openclaw versions < 2026.3.1. Fixed in 2026.3.1. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
OpenClaw is an open-source package designed for browser control, allowing users to automate and manage web interactions. It provides a range of functionalities, including the ability to evaluate actions within a browser context. However, a critical vulnerability has been identified that could allow unauthorized access to browser-control routes, compromising the security of deployments that rely on this package.
Vulnerability Detail
The vulnerability arises when OpenClaw attempts to bootstrap authentication automatically upon startup without explicit credentials. If this bootstrap process encounters an error, the application may continue to start up, exposing sensitive browser-control routes without requiring authentication. This could allow a local process or a loopback-reachable SSRF path to access evaluate-capable actions, leading to potential unauthorized actions within the browser context.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading 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.1
This is the first release that contains the fix.
npm install openclaw@2026.3.1Tip — 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. The best course of action is to update to the patched version as soon as possible.
Conclusion
In summary, the OpenClaw package has a significant vulnerability that could allow unauthorized access to browser-control routes if authentication fails during startup. Users are strongly advised to update to version 2026.3.1 or later to secure their deployments. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows unauthorized access to browser-control routes if the authentication bootstrap fails during startup.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
The CVSS score for this vulnerability is 6.9, indicating a moderate level of risk.
While there are no specific workarounds, it is crucial to prioritize updating to the patched version to mitigate the risk.
Vulert monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file, without requiring access to the code or installation.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
