CVE-2026-48716Public exploitNetwork attack vector

Arbitrary file write via WhatsApp filename traversal

Published Jun 18, 2026 · Updated Jun 18, 2026

Path traversal in the nanobot WhatsApp bridge 0.1.5.post3 and earlier allows remote attackers to write files via crafted document names. The bridge/src/whatsapp.ts downloadMedia path concatenates documentMessage.fileName into outFilename, normalizes it with path.join, and passes the result to writeFile without a basename or directory-boundary check. Any whitelisted WhatsApp sender, or any sender when allow_from is "*", can overwrite process-accessible files with attacker-controlled bytes without user interaction.

CVSS severity8.7
High
EPSS probability0.42%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path traversal in the nanobot WhatsApp bridge 0.1.5.post3 and earlier allows remote attackers to write files via crafted document names. The bridge/src/whatsapp.ts downloadMedia path concatenates documentMessage.fileName into outFilename, normalizes it with path.join, and passes the result to writeFile without a basename or directory-boundary check. Any whitelisted WhatsApp sender, or any sender when allow_from is "*", can overwrite process-accessible files with attacker-controlled bytes without user interaction.

The record

CVE
CVE-2026-48716
Published
Jun 18, 2026
Updated
Jun 18, 2026
Vendor
Data Intelligence Lab @ HKU
Product
nanobot
Classifications
CWE-22, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=<= 0.1.5.post3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Data Intelligence Lab @ HKU · nanobotversion=<= 0.1.5.post3

Published CVSS scores

8.7GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo