Live › vulnerability › CVE-2026-121550
nnn, a terminal file manager, accepts an existing NNN_FIFO path without checking it is a FIFO. A local attacker who pre-creates the predictable /tmp/nnn.fifo as a symlink can overwrite files the victim can write or learn which paths the victim browses.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 16:21 UTC. All times on this page are UTC.
Only machines where a local user can write to /tmp and where nnn runs with the predictable FIFO path in use. The sources describe a local attacker on a shared system, not a remote one. Single-user machines are unlikely to be exposed.
No product ranges from the sources yet.
nnn -V or nnn --version and compare against the versions in the sourcesEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
nnn through 5.3 contains an insecure file handling vulnerability that allows local attackers to redirect writes because main() accepts an existing NNN_FIFO path without verifying it is a FIFO. Attackers can pre-create the documented predictable /tmp/nnn.fifo path as a symlink or readable regular file, causing victim-writable files to be overwritten or leaking the victim's browsed paths.
This page as .md · .json · in your agent: get_signal("CVE-2026-121550")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.