CVE-2026-121864

Nanobot Sandbox Escape via Caller-Selected Shell Executable

Published Nov 17, 2026 CVSS 4.0 · 7.7 High EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

When nanobot is configured to use sandboxed execution, the selected shell program is launched before the sandbox environment is enforced. The caller can specify an arbitrary shell executable path, and the agent creates a runnable file in its workspace. An attacker who can influence this process can point the shell parameter to the newly created executable, causing the program to run with the same operating‑system privileges as the nanobot process and outside the intended sandbox. This bypass defeats the sandbox protection and allows the attacker to perform arbitrary operations with nanobot's privileges.

Affected Systems

Affecting HKUDS nanobot (nanobot‑ai) from version 0.2.1 up to but not including 0.4.1. No other vendors or products are listed among the affected items.

Risk and Exploitability

The CVSS score of 7.7 indicates high severity, but the EPSS value is not reported, and the vulnerability is not in the CISA KEV catalog. Exploitation requires the attacker to control or influence the agent's workspace to supply a controlled shell executable, implying a local or authenticated attacker context. The weakness is classified as CWE‑73 Input Redirection.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade nanobot to version 0.4.1 or later to apply the fix that prevents user-specified shell execution before sandboxing.
  • If an upgrade cannot be performed immediately, disable the sandboxed exec feature or remove the configuration that allows selecting a custom shell to eliminate the attack path.
  • Restrict file creation permissions in the agent workspace to trusted users and enforce input validation or naming rules to prevent malicious executable injection.

Generated by OpenCVE AI on November 17, 2026 at 10:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Hkuds
Hkuds nanobot
Vendors & Products Hkuds
Hkuds nanobot
Type Values Removed Values Added
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.
Title Nanobot Sandbox Escape via Caller-Selected Shell Executable
Weaknesses CWE-73
References
Metrics cvssV3_1

{'score': 8.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-73

    External Control of File Name or Path

Sources

Status
PUBLISHED
Assigner
tenable
Published
Updated
Nov 17, 2026, 8:49 AM
Reserved
Nov 4, 2026, 9:50 AM
Status
Deferred
Published
Nov 17, 2026, 9:17 AM
Modified
Nov 17, 2026, 9:17 AM