openclaw
Affected
- introduced
0, fixed2026.2.25(semver)
Fixed versions
2026.2.25
Fix
- Fixed version
2026.2.25npm install [email protected]
Advisory
Also known as: CVE-2026-32025
OpenClaw's browser-origin WebSocket auth hardening gap could enable loopback password brute-force chains
This issue is a browser-origin WebSocket auth chain on local loopback deployments using password auth. It is serious, but conditional: an attacker must get the user to open a malicious page and then successfully guess the gateway password.
Context and Preconditions
OpenClaw’s web/gateway surface is designed for local use and trusted-operator workflows. In affected versions, a browser-origin client could combine three behaviors:
Successful exploitation requires all of the following:
Practical Impact
If the password is guessed, an attacker can establish an authenticated operator WebSocket session and invoke control-plane methods available to that role. This is not an unauthenticated internet-exposed RCE class issue by itself; it is a local browser-origin auth-hardening gap with meaningful impact under the conditions above.
Affected Packages / Versions
openclaw (npm)<=2026.2.24 (latest published npm version as of February 26, 2026)>=2026.2.25Fix Commit(s)
c736f11a16d6bc27ea62a0fe40fffae4cb071fdbFix Details
Release Process Note
patched_versions is pre-set to the planned next npm release (2026.2.25) so once that release is published, the advisory is published.
OpenClaw thanks @luz-oasis for reporting.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.25 (semver)2026.2.25
2026.2.25npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0