CVE-2026-121865: Nanobot WebSocket Client Workspace Authorization Bypass
In nanobot, the WebSocket gateway allows a standard client holding a valid client token to select an existing directory outside the operator-configured workspace as the root of a new conversation. The agent can then read and expose files in that directory that are readable by the nanobot service account.
This issue affects nanobot (nanobot-ai) from 0.3.5 before 0.4.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.4.1
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
nanobot-ai versions 0.3.5 through versions before 0.4.1 are affected. Exposure requires that a client can connect to the WebSocket gateway with a valid standard client token.
What access does an attacker need?
An attacker needs a valid client token; no elevated operator-level access is described. They can select an existing directory outside the configured workspace when creating a new conversation.
What data could be exposed?
The agent can read and expose files in the selected directory that are readable by the nanobot service account. Files not readable by that service account are not described as exposed.
What should be done if patching cannot happen immediately?
Restrict access to valid client tokens and the WebSocket gateway, and reduce the nanobot service account's filesystem permissions to only the directories it needs. This limits both who can invoke the vulnerable workflow and which files could be read.