Gnu Nano vulnerabilities

CVE-2024-5742 [MEDIUM] CWE-59 CVE-2024-5742: A vulnerability was found in GNU Nano that allows a possible privilege escalation through an insecur A vulnerability was found in GNU Nano that allows a possible privilege escalation through an insecure temporary file. If Nano is killed while editing, a file it saves to an emergency file with the permissions of the running user provides a window of opportunity for attackers to escalate privileges through a malicious symlink.

CVE-2026-6843 [MEDIUM] CWE-134 CVE-2026-6843: A flaw was found in nano. A local user could exploit a format string vulnerability in the `statuslin A flaw was found in nano. A local user could exploit a format string vulnerability in the `statusline()` function. By creating a directory with a name containing `printf` specifiers, the application attempts to display this name, leading to a segmentation fault (SEGV). This results in a Denial of Service (DoS) for the `nano` application.

CVE-2010-1161 [LOW] CWE-362 CVE-2010-1161: Race condition in GNU nano before 2.2.4, when run by root to edit a file that is not owned by root, Race condition in GNU nano before 2.2.4, when run by root to edit a file that is not owned by root, allows local user-assisted attackers to change the ownership of arbitrary files via vectors related to the creation of backup files.

CVE-2026-40556 [LOW] CWE-732 CVE-2026-40556: GNU nano creates the user’s ~/.local directory with overly permissive permissions when the directory GNU nano creates the user’s ~/.local directory with overly permissive permissions when the directory does not exist yet. On first use of features requiring Cross-Desktop Group (XDG) data storage, nano explicitly requests directory mode 0777, making the directory world‑writable in environments where the process umask does not sufficiently restrict permi

CVE-2010-1160 [LOW] CWE-59 CVE-2010-1160: GNU nano before 2.2.4 does not verify whether a file has been changed before it is overwritten in a GNU nano before 2.2.4 does not verify whether a file has been changed before it is overwritten in a file-save operation, which allows local user-assisted attackers to overwrite arbitrary files via a symlink attack on an attacker-owned file that is being edited by the victim.