Aggregates CVE and security vulnerability intelligence across all mutt-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Historical issues mainly involve vendor risk buffer overflow, vendor risk memory corruption, vendor risk input validation, and vendor risk path handling and related problems; some flaws may lead to vendor impact memory corruption.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2024-49395 | In mutt and neomutt, PGP encryption does not use the --hidden-recipient mode which may leak the Bcc email header field by inferring from the recipients info. | [email protected] | 5.3 | 0.05% | 2024-11-12 | 2024-11-14 |
| CVE-2024-49394 | In mutt and neomutt the In-Reply-To email header field is not protected by cryptographic signing which allows an attacker to reuse an unencrypted but signed email message to impersonate the original sender. | [email protected] | 5.3 | 0.05% | 2024-11-12 | 2024-11-14 |
| CVE-2024-49393 | In neomutt and mutt, the To and Cc email headers are not validated by cryptographic signing which allows an attacker that intercepts a message to change their value and include himself as a one of the recipients to compromise message confidentiality. | [email protected] | 6.5 | 0.05% | 2024-11-12 | 2025-07-16 |
| CVE-2023-4875 | Null pointer dereference when composing from a specially crafted draft message in Mutt >1.5.2 <2.2.12 | [email protected] | 2.2 | 0.03% | 2023-09-09 | 2024-11-21 |
| CVE-2023-4874 | Null pointer dereference when viewing a specially crafted email in Mutt >1.5.2 <2.2.12 | [email protected] | 4.3 | 0.08% | 2023-09-09 | 2024-11-21 |
| CVE-2022-1328 | Buffer Overflow in uudecoder in Mutt affecting all versions starting from 0.94.13 before 2.2.3 allows read past end of input line | [email protected] | 4.3 | 0.27% | 2022-04-14 | 2024-11-21 |
| CVE-2021-32055 | Mutt 1.11.0 through 2.0.x before 2.0.7 (and NeoMutt 2019-10-25 through 2021-05-04) has a $imap_qresync issue in which imap/util.c has an out-of-bounds read in situations where an IMAP sequence set ends with a comma. NOTE: the $imap_qresync setting for QRESYNC is not enabled by default. | [email protected] | 9.1 | 0.36% | 2021-05-05 | 2024-11-21 |
| CVE-2021-3181 | rfc822.c in Mutt through 2.0.4 allows remote attackers to cause a denial of service (mailbox unavailability) by sending email messages with sequences of semicolon characters in RFC822 address fields (aka terminators of empty groups). A small email message from the attacker can cause large memory consumption, and the victim may then be unable to see email messages from other persons. | [email protected] | 6.5 | 2.80% | 2021-01-19 | 2024-11-21 |
| CVE-2020-28896 | Mutt before 2.0.2 and NeoMutt before 2020-11-20 did not ensure that $ssl_force_tls was processed if an IMAP server's initial server response was invalid. The connection was not properly closed, and the code could continue attempting to authenticate. This could result in authentication credentials being exposed on an unencrypted connection, or to a machine-in-the-middle. | [email protected] | 5.3 | 0.10% | 2020-11-23 | 2024-11-21 |
| CVE-2020-14954 | Mutt before 1.14.4 and NeoMutt before 2020-06-19 have a STARTTLS buffering issue that affects IMAP, SMTP, and POP3. When a server sends a "begin TLS" response, the client reads additional data (e.g., from a man-in-the-middle attacker) and evaluates it in a TLS context, aka "response injection." | [email protected] | 5.9 | 4.79% | 2020-06-21 | 2024-11-21 |
| CVE-2020-14154 | Mutt before 1.14.3 proceeds with a connection even if, in response to a GnuTLS certificate prompt, the user rejects an expired intermediate certificate. | [email protected] | 4.8 | 0.66% | 2020-06-15 | 2024-11-21 |
| CVE-2020-14093 | Mutt before 1.14.3 allows an IMAP fcc/postpone man-in-the-middle attack via a PREAUTH response. | [email protected] | 5.9 | 3.86% | 2020-06-15 | 2024-11-21 |
| CVE-2005-2351 | Mutt before 1.5.20 patch 7 allows an attacker to cause a denial of service via a series of requests to mutt temporary files. | [email protected] | 5.5 | 0.13% | 2019-11-01 | 2024-11-20 |
| CVE-2018-14362 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c does not forbid characters that may have unsafe interaction with message-cache pathnames, as demonstrated by a '/' character. | [email protected] | 9.8 | 1.81% | 2018-07-17 | 2024-11-21 |
| CVE-2018-14359 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They have a buffer overflow via base64 data. | [email protected] | 9.8 | 4.10% | 2018-07-17 | 2024-11-21 |
| CVE-2018-14358 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long RFC822.SIZE field. | [email protected] | 9.8 | 1.38% | 2018-07-17 | 2024-11-21 |
| CVE-2018-14357 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They allow remote IMAP servers to execute arbitrary commands via backquote characters, related to the mailboxes command associated with an automatic subscription. | [email protected] | 9.8 | 2.53% | 2018-07-17 | 2024-11-21 |
| CVE-2018-14356 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c mishandles a zero-length UID. | [email protected] | 9.8 | 0.88% | 2018-07-17 | 2024-11-21 |
| CVE-2018-14355 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/util.c mishandles ".." directory traversal in a mailbox name. | [email protected] | 5.3 | 0.81% | 2018-07-17 | 2024-11-21 |
| CVE-2018-14354 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They allow remote IMAP servers to execute arbitrary commands via backquote characters, related to the mailboxes command associated with a manual subscription or unsubscription. | [email protected] | 9.8 | 2.53% | 2018-07-17 | 2024-11-21 |