NanoClaw version 1.2.0 and prior contains a host/container filesystem boundary vulnerability in outbound attachment handling and outbox cleanup that allows a compromised or prompt-injected container to read files outside the intended outbox directory by supplying crafted messages_out.id and content.files values or creating symlinked outbox files. Attackers can exploit this vulnerability to trigger host-side reads of arbitrary files and in some cases achieve recursive deletion of paths outside the intended cleanup target.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/qwibitai/nanoclaw/commit/7814e45570edf0024a1a5c2ba9fbc9cb3a49f7f7 Patch
- https://github.com/qwibitai/nanoclaw/pull/2001 Issue Tracking, Patch
- https://github.com/qwibitai/nanoclaw/pull/2001 Issue Tracking, Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.3 · nanocoNVD modified 2026-10-26 19:10
Affected (CPE criteria) 1
cpe:2.3:a:nanoco:nanoclaw:*:*:*:*:*:*:*:*
References 4
- https://github.com/qwibitai/nanoclaw/commit/7814e45570edf0024a1a5c2ba9fbc9cb3a49f7f7 Patch
- https://github.com/qwibitai/nanoclaw/pull/2001 Issue Tracking, Patch
- https://github.com/qwibitai/nanoclaw/releases/tag/v1.2.0 Product, Release Notes
- https://github.com/qwibitai/nanoclaw/pull/2001 Issue Tracking, Patch