CVE-2026-121864: HKUDS nanobot · External Control of File Name or Path
Affects HKUDS nanobotSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 0.4.1 soon.
Data as of 17 Nov 2026, 09:05 UTC
Thin evidence
One scorer or none| CNA (tenable) | CVSS 3.1 | 8.5 |
|---|---|---|
| CNA (tenable) | CVSS 4.0 | 7.7 |
- Patch
- Available – fixed in 0.4.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade nanobot and nanobot-ai to 0.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nanobotnanobot-ai | Affected
| Fixed in
|
PyPInanobot-aipkg:pypi/nanobot-aiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade nanobot to version 0.4.1 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-121864 is a high-severity vulnerability in nanobot versions from 0.2.1 up to but not including 0.4.1. When sandboxed execution is enabled, the shell executable used to run commands can be chosen by an attacker and launched before sandbox restrictions are applied. This allows an attacker to run arbitrary executables outside the sandbox with the permissions of the nanobot process, potentially leading to full system compromise. The issue is fixed in version 0.4.1.