CVE
HKUDS Nanobot AI authorization bypass in WebSocket workspace handling
Affects nanobot 0.3.5 and 0.4.0 (before 0.4.1) when gateway access and a valid client token are involved. Fixed in 0.4.1.
Written by a model from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
- Exploited
- No known exploitation
- Fix
- Fixed in 0.4.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Nanobot releases 0.3.5 and 0.4.0 (affected range 0.3.5 before 0.4.1). Gateway access and a valid client token are required.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.30% · 23rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 12% of nanobot-ai downloads last week were affected versions (2.1K).PyPI, per-version counts from ClickPy, 18.5K downloads in the last 7 days, read Nov 14, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The nanobot WebSocket gateway in the nanobot-ai package from HKUDS lets a remote attacker with a valid client token choose a directory outside the configured workspace as the root of a new conversation. The agent can then read and expose files in that directory that the nanobot service account can read.
Original description
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.
Who should check
Teams running nanobot-ai 0.3.5 through 0.4.0 with the WebSocket gateway, where clients hold client tokens.
“In the confirmed affected releases 0.3.5 and 0.4.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects PyPI packages
- Severity7.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 33 if CISA's SSVC rates it automatable
Impact
- Widely used
nanobot-ai has 17.1k weekly downloads.Source: pypistats.org
5 packages depend on nanobot-ai.Source: deps.dev
What to do
Check whether your setup matches what the bug needs.
Nanobot releases 0.3.5 and 0.4.0 (affected range 0.3.5 before 0.4.1). Gateway access and a valid client token are required.Upgrade to a fixed version: 0.4.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-121865 (Nanobot WebSocket Client Workspace Authorization Bypass), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-121865 (entry last updated 2026-11-17):
Affected:
- PyPI package nanobot-ai: from 0.3.5, fixed in 0.4.1
Fixed versions: 0.4.1.
Conditions (all must be true for the bug to be hit):
- Nanobot releases 0.3.5 and 0.4.0 (affected range 0.3.5 before 0.4.1). (source: https://github.com/HKUDS/nanobot/security/advisories/GHSA-hg87-wf6q-3m38)
- Gateway access and a valid client token are required. (source: https://github.com/HKUDS/nanobot/security/advisories/GHSA-hg87-wf6q-3m38)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-121865 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121865 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.tenable.com/security/research/tra-2026-69
- https://github.com/HKUDS/nanobot/security/advisories/GHSA-hg87-wf6q-3m38
- https://github.com/HKUDS/nanobot/releases/tag/v0.4.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-121865
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121865"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nanobot-aiPyPI
From 0.3.5 · fixed in 0.4.1
Fixed in 0.4.1 (released Nov 6, 2026, 11 days before disclosure).
The latest release, 0.4.1, is not affected.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121865
Is CVE-2026-121865 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A client can choose an existing directory outside the configured workspace as the conversation root, and the agent can then expose files there that the nanobot service account can read.Source: github.com
Which versions are affected by CVE-2026-121865?
nanobot-ai (PyPI): from 0.3.5 before 0.4.1.Source: cve.now feed data
Am I affected, and how do I check?
Releases 0.3.5 and 0.4.0 are affected (the affected range is 0.3.5 before 0.4.1). The issue requires gateway access and a valid client token, and the installed nanobot-ai version can be checked to see which release is in use.Source: github.com
How do I fix CVE-2026-121865?
Upgrade nanobot-ai to 0.4.1 or later using the existing installation method, and restart the gateway.Source: github.com