CVE-2026-48716

NVD description

nanobot is a personal AI assistant. In versions 0.1.5.post3 and prior, the WhatsApp bridge in bridge/src/whatsapp.ts constructs a filesystem path using the fileName field from an incoming WhatsApp document message without sanitization. The WhatsApp bridge downloads media attachments and writes them to disk using a filename derived from the sender's message via documentMessage.fileName, which is concatenated with a prefix and its raw value is passed directly to path.join(mediaDir, outFilename). Node.js path.join resolves .. components, allowing an attacker to escape the intended media/ directory by sending a document with a crafted fileName such as ../../../.ssh/authorized_keys. Because the attacker also controls the file content (the downloaded buffer), this is a write-anywhere primitive — both path and content are attacker-controlled. A fix for this issue is planned for version 0.1.5.post4.

What to do

• NVD lists no fixed version yet: follow the vendor advisory below and keep Nanobot off the public internet until a fix ships.
• Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

• NVD: CVE-2026-48716
• https://github.com/HKUDS/nanobot/security/advisories/GHSA-3f63-vcp3-hvqr

Other Nanobot CVEs