An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is heap exposure in nested MIME comment parsing. An authenticated IMAP user could craft an email message containing an RFC 822 comment ending with a backslash. When parsing the message, the server would read past the message's end in memory, and read into the heap, returning the read content to the user.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Thu, 16 Jul 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 16 Jul 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is heap exposure in nested MIME comment parsing. An authenticated IMAP user could craft an email message containing an RFC 822 comment ending with a backslash. When parsing the message, the server would read past the message's end in memory, and read into the heap, returning the read content to the user. | |
| First Time appeared |
Cyrusimap
Cyrusimap cyrus Imap |
|
| Weaknesses | CWE-126 | |
| CPEs | cpe:2.3:a:cyrusimap:cyrus_imap:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Cyrusimap
Cyrusimap cyrus Imap |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-07-16T19:01:31.618Z
Reserved: 2026-05-18T00:00:00.000Z
Link: CVE-2026-47088
Updated: 2026-07-16T19:01:27.907Z
No data.
No data.
OpenCVE Enrichment
No data.
Weaknesses