CVE-2026-121865nanobot-ai >= 0.3.5, Incorrect Authorization
NVD
Vulnerability Summary
Impact In the confirmed affected releases 0.3.5 and 0.4.0, a standard WebSocket client with a valid client token could select an existing directory outside the operator-configured workspace as the root of a new conversation. The agent could then expose files in that directory that are readable by the nanobot service account. The issue requires gateway access and a valid client token; it does not bypass operating-system file permissions. Earlier releases are still being assessed and are not established to be unaffected. Patches Upgrade `nanobot-ai` to 0.4.1 or later using the existing installation method, and restart the gateway. The fix restricts ordinary clients to their configured workspace authority. Credits Thanks to Tenable Research for reporting and validating this issue. CVE-2026-121865.
CVSS v3.1 Base Metrics — Score 7.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:LAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityLow
AvailabilityLow
Affected & Patched Versions
- nanobot-ai >= 0.3.5, <= 0.4.0
- nanobot-ai 0.4.1
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run nanobot-ai >= 0.3.5, and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 8, 2026Published
- Nov 8, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new nanobot-ai >= 0.3.5, CVEsYou are reading CVE-2026-121865. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
Data last checked: Nov 14, 2026 02:01 UTC