Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAttacker sets up malicious IMAP server
-
DeliveryUser connects to Mutt with CRAM-MD5 enabled
-
ExploitServer sends authentication challenge
-
InstallMutt computes MD5 digest from password and challenge
-
C2strfcpy truncates digest at first null byte
-
ExecuteAttacker pre-computed response using truncated digest matches
-
ImpactAuthentication succeeds with forged credentials
-
Step 8Attacker gains mail access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Metacharacter neutralization
|
| Exploitation Conditions | Exploitation requires: (1) IMAP CRAM-MD5 authentication must be enabled and attempted (not all mail servers or Mutt configurations use this method); (2) the attacker must either operate a malicious IMAP server the user connects to, or be positioned on-path to intercept and manipulate IMAP traffic; (3) the naturally occurring MD5 digest must contain a null byte at a position that reduces authentication security (the probability depends on the specific password and challenge, making this non-deterministic); (4) the targeted mail server must accept the truncated digest as valid authentication, which depends on server-side validation logic. In typical deployments, authenticated users with configured IMAP servers of their choice face minimal risk; users connecting to untrusted or user-specified servers face higher (though still complexity-limited) risk. Default Mutt configurations may or may not enable CRAM-MD5; this depends on compile-time options and mail server advertisement. |
| Impact | This vulnerability presents minimal real-world risk despite network-accessible attack vector. CVSS 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) reflects high attack complexity (AC:H), indicating the attacker must satisfy difficult conditions - specifically, the MD5 digest must naturally contain a null byte in a position that causes meaningful truncation. The tag 'Information Disclosure' conflicts with the CVSS confidentiality impact (C:N), suggesting integrity compromise rather than confidentiality breach. The impact is limited to integrity (I:L), not system availability or core confidentiality. No EPSS score, KEV status, or public exploit availability reported; this is a 'quiet' vulnerability unlikely to be actively exploited in the wild. The attack requires either (1) the user to authenticate against a malicious IMAP server that crafts specific challenges, or (2) an on-path attacker to intercept and manipulate IMAP traffic. Defenders should assess Mutt's role in their environment: if IMAP is used only internally or with trusted servers, risk is negligible. For external or untrusted IMAP access, the AC:H barrier remains high. |
| Exploit ScenarioDerived | An attacker operates a malicious IMAP server and tricks a Mutt user into connecting (via misconfigured server list or phishing). When the server initiates CRAM-MD5 authentication, it sends a challenge crafted so that the resulting MD5 digest contains a null byte early in its byte sequence. Mutt's strfcpy truncates the digest at that null byte, shortening the authentication material. The attacker, knowing this truncation, pre-computes a response using the truncated digest and sends it, potentially allowing authentication bypass or credential forgery. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 04, 2026
Mutt before 2.3.2 uses an unsafe string copy function (strfcpy) instead of memcpy when handling MD5 digest data in IMAP CRAM authentication, allowing attackers to potentially forge IMAP credentials by triggering buffer manipulation during the authentication handshake. The vulnerability requires manual connection attempt to a malicious IMAP server and affects network IMAP authentication flows, though the low CVSS score (3.7) reflects high attack complexity and integrity impact only.
RemediationAI
Upgrade Mutt to version 2.3.2 or later, which replaces the strfcpy call with memcpy in the IMAP CRAM-MD5 authentication function (commit 834c5a2ed0479e51e8662a31caed129f136f4805). Users unable to upgrade immediately should restrict IMAP authentication to trusted, internal mail servers and enable TLS/SSL encryption for all IMAP connections to reduce the attack surface. Disabling CRAM-MD5 authentication in favor of other mechanisms (PLAIN over TLS, OAuth2) is a workaround if the mail server supports alternatives, though this reduces authentication security if TLS is not enforced. The trade-off of disabling CRAM-MD5 is loss of a non-plaintext authentication option; verify server support before applying this mitigation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Mutt's IMAP CRAM-MD5 authentication mechanism uses strfcpy (a string-safe copy function designed to null-terminate strings) to copy binary MD5 digest data into a buffer. strfcpy interprets the digest data as a C string and stops copying at the first null byte encountered, potentially truncating the cryptographic hash. The correct function, memcpy, performs fixed-length binary copying without null-byte interpretation. The vulnerability resides in imap/auth_cram.c line 152 (per commit 834c5a2), where strfcpy was called on a 16-byte MD5 digest (MD5_DIGEST_LEN) that may contain null bytes. CWE-158 (Improper Neutralization of Null Byte or NUL Character) categorizes this flaw: the null bytes within the binary digest are incorrectly interpreted as string terminators, truncating the authentication material.
Know when Mutt gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
mutt before 2.3.2 sometimes uses strfcpy instead of memcpy for the IMAP auth_cram MD5 digest.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. Rated critical severity (CVSS 9.8), this vu
The write_one_header function in mutt 1.5.23 does not properly handle newline characters at the beginning of a header, w
EUVD-2026-26895
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB