OpenClaw WebSocket Session Vulnerability: Token Rotation Issue

openclaw Updated 09 Apr 2026

Summary

09/04/2026
MODERATE
Yes i
Moderate
5.9

GHSA-5h3f-885m-v22w: OpenClaw: Existing WS sessions survive shared gateway token rotation. Affects openclaw versions < 2026.4.8. Fixed in 2026.4.8. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

OpenClaw is a user-controlled local assistant designed to facilitate various tasks for users. It operates by utilizing WebSocket connections to maintain real-time communication. However, a significant vulnerability exists where existing WebSocket sessions do not terminate upon the rotation of the shared gateway token, potentially allowing unauthorized access to ongoing sessions.

Vulnerability Detail

The vulnerability arises from the failure to disconnect existing shared-token WebSocket sessions when the shared gateway token is rotated. This oversight can lead to unauthorized access, as users may still be able to interact with the system through these active sessions, even after a token change intended to enhance security. The issue is particularly concerning within the OpenClaw trust model, which does not assume a multi-tenant service boundary, thus increasing the risk for users relying on this local assistant.

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

This is the first release that contains the fix.

npm install openclaw@2026.4.8

Tip — 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. It is strongly recommended to update to the patched version to mitigate the risk.

Conclusion

In summary, the OpenClaw vulnerability related to WebSocket session management poses a significant risk due to the failure to terminate sessions upon token rotation. Users are advised to update to the patched version 2026.4.8 to ensure their systems are secure. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows existing WebSocket sessions to remain active even after the shared gateway token is rotated, potentially leading to unauthorized access.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

While there are no specific workarounds, it is crucial to prioritize updating to the patched version as soon as possible to mitigate the risks associated with this vulnerability.

The CVSS score for this vulnerability is 5.9, indicating a moderate level of risk.

The vulnerability was reported by @kexinoh of Tencent zhuque Lab, highlighting the importance of community involvement in identifying security issues.

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

This is the first release that contains the fix.

npm install openclaw@2026.4.8

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