Unauthorized Node Event Injection Vulnerability in OpenClaw Package

openclaw Updated 04 Mar 2026

Summary

03/03/2026
MODERATE
Yes i
Moderate
5.4

GHSA-rv2q-f2h5-6xmg: OpenClaw's Node role device-identity bypass allows unauthorized node.event injection. Affects openclaw versions < 2026.2.22. Fixed in 2026.2.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 Penetration testing for web, API and mobile 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 framework designed for building voice-enabled applications. It facilitates communication between devices and agents through WebSocket connections. The package allows for role-based access control, enabling different functionalities based on the user's role. However, a recent vulnerability has been identified that permits unauthorized access to certain functionalities without proper device identity verification.

Vulnerability Detail

The vulnerability arises from a flaw in the WebSocket connection process, which allows clients authenticated with a shared gateway token to connect as 'role=node' without requiring device identity or pairing. This unauthorized access enables clients to invoke 'node.event', which can trigger agent requests and voice transcript flows. The lack of restrictions on role assignment during the handshake process poses significant security risks, as it allows for potential unauthorized event injections that could lead to unintended agent executions.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.22

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

Workaround

As a temporary workaround, it is recommended to restrict access to the WebSocket connection for clients that do not have a valid device identity. Implementing additional checks on the server-side to validate device pairing before allowing 'role=node' connections can mitigate the risk until the package is updated.

Conclusion

The unauthorized node event injection vulnerability in the OpenClaw package poses a significant security risk by allowing clients to bypass device identity checks. It is crucial to upgrade to the patched version 2026.2.22 to mitigate this risk. Additionally, implementing server-side checks can provide a temporary solution until the upgrade is completed.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The vulnerability allows unauthorized clients to connect as 'role=node' without device identity, enabling them to inject events into the system.

Unauthorized event injections can trigger agent executions and voice transcript flows, potentially leading to data leaks or unintended actions.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The CVSS score for this vulnerability is 5.4, indicating a moderate severity level.

Using tools like Vulert, which monitors your package-lock.json file, can help you receive real-time alerts for open-source vulnerabilities in your software.

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

This is the first release that contains the fix.

npm install openclaw@2026.2.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