NitroShare Desktop through version 0.3.4 contains a high-severity path traversal flaw in its LAN file transfer server that allows unauthenticated attackers on the same network to write arbitrary files outside the intended transfer directory. The issue stems from improper validation of crafted filenames supplied in the JSON item header name field, enabling ../ traversal sequences to target any location writable by the current user. Public reporting says the service listens on TCP port 40818 on all network interfaces by default, with TLS typically disabled, leaving transfers unauthenticated in common deployments.
The vulnerability is tracked as CVE-2026-66050 and has been described as remotely exploitable, with severity scores of 8.7 CVSS 4.0 and 7.5 CVSS 3.1. Advisories warn that attackers could place files in the Windows Startup folder to establish persistence and trigger code execution at the next user login, and a public proof-of-concept was reportedly validated against NitroShare 0.3.4 on Windows. The recommended mitigation is to upgrade to a version newer than 0.3.4 and monitor systems for unauthorized file writes.

See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Public advisories disclosed CVE-2026-66050 affecting NitroShare Desktop through version 0.3.4. The vulnerability allows unauthenticated attackers on the same network to write arbitrary files outside the transfer directory via a crafted filename in the LAN file transfer server, potentially enabling persistence or code execution.
A GitHub repository documented and demonstrated a path traversal vulnerability in NitroShare Desktop v0.3.4, including a proof-of-concept verified on Windows. The write-up described unauthenticated arbitrary file write via crafted ../ sequences in the LAN file transfer server's JSON item header.
The GitHub write-up states the author attempted responsible disclosure to the NitroShare developer three times during April and May 2026 but received no response.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcevulncheck.com
Open sourcegithub.com
Open sourceseclists.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.