mutt vulnerabilities

Use of Out-of-range Pointer Offset in mutt

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.

CVE-2026-43864

mutt before 2.3.2 has a show_sig_summary NULL pointer dereference.

CVE-2026-43863

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

CVE-2026-43862

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

CVE-2026-43861

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

CVE-2026-43860

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

CVE-2026-43859

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

Mutt: neomutt: bcc email header field is indirectly leaked by cryptographic info block

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.

Mutt: neomutt: in-reply-to email header field it not protected by cryptograpic signing

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.

Mutt: neomutt: to and cc email header fields are not protected by cryptographic signing

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.

Undefined Behavior for Input to API in Mutt

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

• Update to 1.9.4-3ubuntu0.6+esm1

Undefined Behavior for Input to API in Mutt

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

• Update to 1.9.4-3ubuntu0.6+esm1