8.7
HIGH CVSS 3.1
CVE-2026-48716
nanobot: Path traversal via unsanitized WhatsApp document fileName enables arbitrary file write
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.

INFO

Published Date :

June 18, 2026, 8:16 p.m.

Last Modified :

June 23, 2026, 3:59 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-48716 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Nanobot nanobot
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 HIGH [email protected]
Solution
Update Nanobot to version 0.1.5.post4 or later to fix path traversal vulnerability.
  • Update Nanobot to version 0.1.5.post4 or later.
  • Sanitize all user-supplied file names.
  • Validate file paths before writing to disk.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-48716.

URL Resource
https://github.com/HKUDS/nanobot/security/advisories/GHSA-3f63-vcp3-hvqr
https://github.com/HKUDS/nanobot/security/advisories/GHSA-3f63-vcp3-hvqr
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-48716 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-48716 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-48716 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Jun. 22, 2026

    Action Type Old Value New Value
    Added Reference https://github.com/HKUDS/nanobot/security/advisories/GHSA-3f63-vcp3-hvqr
    Added SSVC {'id': 'CVE-2026-48716', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'poc'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-06-22T15:40:56.174780Z'}
  • New CVE Received by [email protected]

    Jun. 18, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'HKUDS', 'product': 'nanobot', 'versions': [{'status': 'affected', 'version': '<= 0.1.5.post3'}]}]
    Added 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.
    Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
    Added CWE CWE-22
    Added Reference https://github.com/HKUDS/nanobot/security/advisories/GHSA-3f63-vcp3-hvqr
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.