VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

nano: vulnerability history, versions and safety

nano is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 28 releases, from Apr 2010 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 23 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nano vulnerabilities

Vulert verdict on nano i

Updated on 23 Oct 2026

Careful: 4 of the 10 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 10 vulnerabilities on record across 16 years, 4 in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 16 years · 4 in the last year i
  • Latest disclosure 23 Jul 2026 i
  • Highest CVSS 6.8 i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for nano, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 28 of 28 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2010 4
  • 2024 2
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for nano

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in Nano Package: CVE-2026-6390 6.8 medium No fix published 23 Jul 2026
Arbitrary File Overwrite in GNU nano N/A unrated 2.2.4-1 16 Apr 2010
Race condition vulnerability in GNU nano N/A unrated 2.2.4-1 16 Apr 2010
Privilege Escalation Vulnerability in GNU Nano: Insecure Temporary File Handling N/A unrated 5.4-2+deb11u3 12 Jun 2024
Symlink Attack Vulnerability in GNU Nano Package N/A unrated 2.2.4-1 16 Apr 2010

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About nano

Is nano safe to use?

Vulert records 10 vulnerabilities for nano in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does nano have?

10 vulnerabilities are recorded for nano in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nano vulnerabilities disclosed?

4 vulnerabilities were recorded for nano in the last 12 months, and the oldest entry in this database dates to 16 Apr 2010. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of nano are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor nano for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the nano version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.