Mail client crash via NULL key dereference
Published May 4, 2026 · Updated May 4, 2026
NULL pointer dereference in Mutt before 2.3.2 allows attackers to crash the mail client while signature status is displayed. The show_sig_summary function dereferences key->subkeys for an expired-key signature even when show_one_sig_status supplies a NULL key after GPG_ERR_NO_PUBKEY. Exploitation requires user interaction and a high-complexity local trigger; the documented consequence is interruption of the Mutt process only.
Summary
What happened
NULL pointer dereference in Mutt before 2.3.2 allows attackers to crash the mail client while signature status is displayed. The show_sig_summary function dereferences key->subkeys for an expired-key signature even when show_one_sig_status supplies a NULL key after GPG_ERR_NO_PUBKEY. Exploitation requires user interaction and a high-complexity local trigger; the documented consequence is interruption of the Mutt process only.
The record
- CVE
- CVE-2026-43864
- Published
- May 4, 2026
- Updated
- May 4, 2026
- Vendor
- Mutt
- Product
- Mutt
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- 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?
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