OS Command Injection Affecting nnn package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.44% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-NNN-19012618
  • published20 Aug 2026
  • disclosed19 Aug 2026

Introduced: 19 Aug 2026

CVE-2026-65612  (opens in a new tab)
CWE-78  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest nnn.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nnn package and not the nnn package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

nnn does not sanitize the filename variable. An attacker can place a file with a crafted name on a shared filesystem, removable media, or inside an extracted archive whose name contains a single quote followed by shell syntax. If the victim navigates to that file and opens it with preview-tabbed, the filename is embedded into the generated shell command and the injected payload executes with the privileges of the nnn process.

Maintainer of this project was notified about this vulnerability. It might has been addressed, but the maintainer did not provide a vulnerable version range. Only version 5.2 was tested and confirmed as vulnerable.