VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

mutt: vulnerability history, versions and safety

mutt is a package in the Debian ecosystem. Vulert records 71 vulnerabilities for it across 15 releases, from Mar 2003 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
71 vulnerabilities recorded U71
i
12 with no fix published

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

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

Most recent disclosure 04 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mutt vulnerabilities

Vulert verdict on mutt i

Updated on 23 Oct 2026

Careful: 12 of the 71 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 71 vulnerabilities on record across 23 years, 6 in the last year.

What to do: Plan around the 12 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 71 over 23 years · 6 in the last year i
  • Latest disclosure 04 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 12 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 mutt, 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 15 of 15 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2003 2
  • 2004 2
  • 2006 6
  • 2007 4
  • 2009 2
  • 2011 2
  • 2014 4
  • 2018 18
  • 2019 2
  • 2020 8
  • 2021 4
  • 2022 2
  • 2023 5
  • 2024 4
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for mutt

The 5 most severe of 71 vulnerabilities recorded for this package

Search all 71 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Memory Allocation Failure in NeoMutt and Mutt Packages 9.8 critical 1.9.1-1 17 Jul 2018
Stack-Based Buffer Overflow in NeoMutt and Mutt Packages 9.8 critical 1.9.1-1 17 Jul 2018
Out-of-Bounds Read Vulnerability in Mutt and NeoMutt Packages 9.1 critical 2.0.5-4.1 05 May 2021
Path Traversal Vulnerability in NeoMutt and Mutt Packages 7.5 high 1.9.1-1 17 Jul 2018
Null Pointer Dereference Vulnerability in Mutt Email Client 6.5 medium 2.0.5-4.1+deb11u3 09 Sep 2023

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 mutt

Is mutt safe to use?

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

How many vulnerabilities does mutt have?

71 vulnerabilities are recorded for mutt in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 71 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 mutt vulnerabilities disclosed?

6 vulnerabilities were recorded for mutt in the last 12 months, and the oldest entry in this database dates to 24 Mar 2003. 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 mutt 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 mutt for upcoming vulnerabilities?

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