CVE-2026-48716
HighCVSS 8.7Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
In versions 0.1.5.post3 and prior, the WhatsApp bridge in nanobot does not sanitize the fileName field from an incoming document message, allowing an attacker to escape the media/ directory by sending a crafted filename.
Risk Assessment
An attacker can write files anywhere on the server, posing a serious risk to the integrity of the system and data.
Recommendation
It is recommended to upgrade to version 0.1.5.post4, which includes a fix for this vulnerability.
Original NVD description (English source)
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.