Vulnerabilities

heap OOB write in convert_file_from_to() via a crafted Content-Type header allows attacker to OOB write when email is used as a template.

mutt before 2.3.2 has a show_sig_summary NULL pointer dereference.

mutt before 2.3.2 has an infinite loop in data_object_to_stream in crypt-gpgme.c.

In mutt before 2.3.2, the imap_auth_gss security level is mishandled.

mutt before 2.3.2 does not check for '\0' in url_pct_decode.

mutt before 2.3.2 sometimes truncates the hash_passwd by one byte for IMAP auth_cram MD5 digest.

mutt before 2.3.2 sometimes uses strfcpy instead of memcpy for the IMAP auth_cram MD5 digest.

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.

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.

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 compr…

Null pointer dereference when viewing a specially crafted email in Mutt >1.5.2 <2.2.12

Null pointer dereference when composing from a specially crafted draft message in Mutt >1.5.2 <2.2.12

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

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.

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 e…

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.

Mutt before 1.14.4 and NeoMutt before 2020-06-19 have a STARTTLS buffering issue that affects IMAP, SMTP, and POP3.

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.

Mutt before 1.14.3 allows an IMAP fcc/postpone man-in-the-middle attack via a PREAUTH response.

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.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16.