CVE-2026-43859 Other in mutt
Low 3.7
Published
Updated
Check this codebase for CVE-2026-43859 and fix it if it is affected.
What it is: CVE-2026-43859 is a low-severity vulnerability in mutt, published on 4 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43859 in the wild and no public exploit code.
Affected product: mutt. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-43859/ (Markdown: https://insights.sbomify.com/CVE-2026-43859/index.md)
Mutt email client uses incorrect string copying for IMAP CRAM-MD5 authentication, potentially causing functional issues or minor security weaknesses.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-43859?
CVE-2026-43859 is a low-severity vulnerability in mutt, published on 4 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
mutt before 2.3.2 sometimes uses strfcpy instead of memcpy for the IMAP auth_cram MD5 digest.
Weakness: CWE-158
Which versions are affected by CVE-2026-43859?
How do I fix CVE-2026-43859?
Upgrade to a fixed version.
Is CVE-2026-43859 being exploited?
There is no known exploitation of CVE-2026-43859 in the wild and no public exploit code.
Sources
Also known as AZL-85587, DEBIAN-CVE-2026-43859, GHSA-rhvq-8hmp-hm8h, UBUNTU-CVE-2026-43859.