Authentication failure via truncated CRAM-MD5 digest
Published May 4, 2026 · Updated May 4, 2026
Off-by-one error in Mutt before 2.3.2 causes IMAP CRAM-MD5 authentication to fail when a long password's digest contains a zero byte. The hmac_md5 function in imap/auth_cram.c copies the 16-byte raw MD5 result with string-oriented strfcpy, which stops at a zero byte and always reserves space for a terminator. The path requires a password longer than 64 bytes; Debian characterizes the outcome as failed authentication in a corner case with no security impact.
Summary
What happened
Off-by-one error in Mutt before 2.3.2 causes IMAP CRAM-MD5 authentication to fail when a long password's digest contains a zero byte. The hmac_md5 function in imap/auth_cram.c copies the 16-byte raw MD5 result with string-oriented strfcpy, which stops at a zero byte and always reserves space for a terminator. The path requires a password longer than 64 bytes; Debian characterizes the outcome as failed authentication in a corner case with no security impact.
The record
- CVE
- CVE-2026-43860
- Published
- May 4, 2026
- Updated
- May 4, 2026
- Vendor
- Mutt
- Product
- Mutt
- Classifications
- CWE-193
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 4, 2026CVE publishedPublication date reported by the CVE source.
- May 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo