NanoClaw < 2.1.17 - Arbitrary File Read via Symlink Following in forwardAttachedFiles
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.8epss 0.1%
exploitation probability
0.1%top 97% of all CVEs
observed exploitation
nono source reports it
In short
NanoClaw versions before 2.1.17 have a flaw where malicious agents can trick the system into copying files by using symbolic links, potentially exposing sensitive files from the host system.
Technical detail
A symlink following vulnerability exists in the forwardAttachedFiles function where filename validation via isSafeAttachmentName is insufficient, permitting container-controlled agents to leverage fs.copyFileSync's symlink traversal to read arbitrary host-accessible files without proper path containment checks.
Summary generated and translated by AI from the official description.
NanoClaw before 2.1.17 contains a symlink following vulnerability in forwardAttachedFiles that allows container-controlled agents to exfiltrate host-readable files. The host validates attachment filenames using only isSafeAttachmentName before copying with fs.copyFileSync, which follows symlinks without containment checks, allowing malicious agents to disclose arbitrary host files.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
nanocoai · nanoclaw