CVE-2026-43859: mutt before 2.3.2 sometimes uses strfcpy instead of memcpy for the IMAP auth_cram MD5 digest
Source GCVE Database
Not known to be exploited · CVSS 3.7 Low · fixed in 2.3.2 : update mutt when convenient.
Data as of 27 Oct 2026, 01:14 UTC
- Affects
- mutt before 2.3.2
- Patch
- Available – fixed in 2.3.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
A fix is available in mutt version 2.3.2 and later. Users should upgrade to version 2.3.2 or newer to remediate this issue. No other mitigation or workaround is indicated.
Description
A vulnerability in mutt versions before 2.3.2 causes the software to sometimes use strfcpy instead of memcpy for the IMAP auth_cram MD5 digest. This issue could lead to integrity problems in the authentication process.