CVE-2026-43862 json
In mutt before 2.3.2, the imap_auth_gss security level is mishandled.
published 2026-05-04 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-26900
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In mutt before 2.3.2, the imap_auth_gss security level is mishandled.
Patch / fix
- mutt mutt 2.3.2
- mutt Debian 13 2.2.13-1+deb13u1
- mutt Debian 14 2.3.2-1
debian advisories DEBIAN-CVE-2026-43862
- mutt SLES for SAP applications 16.0, SLES 16.0 2.2.16-160000.2.1
suse advisories SUSE-SU-2026:22340-1
- mutt openSUSE Leap 16.0 2.2.16-160000.2.1
- mutt openSUSE Tumbleweed 2.3.2-1.1
opensuse advisories openSUSE-SU-2026:21016-1openSUSE-SU-2026:10695-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-43862 updated cvss 3.7
mutt: Mutt: Security bypass due to mishandled IMAP authentication
-
Red Hat Enterprise Linux 6 muttaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 mutt Red Hat Enterprise Linux 8 mutt Red Hat Enterprise Linux 9 mutt Red Hat Enterprise Linux 10 muttaffected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- mutt mutt
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
Sources
- CVE List CVE-2026-43862
- NVD CVE-2026-43862
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.