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.
Published: 2026-07-16
Score: 3.1 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an authenticated IMAP user to craft an email containing an RFC 822 comment that ends with a backslash. While parsing the message, the Cyrus IMAP server erroneously reads past the message’s boundary into adjacent heap memory and returns that data to the user. This results in the disclosure of potentially sensitive information that was present in heap memory, which could include private data or system secrets.

Affected Systems

Cyrus IMAP software versions up to and including 3.12.2 are affected. The fix is delivered in the 3.12.3 release and later versions.

Risk and Exploitability

The CVSS score is 3.1, indicating low overall severity. The EPSS score is below 1%, suggesting a very low probability of exploitation in the wild. The issue requires authentication to the IMAP service and the ability to send a specially crafted message; therefore, the attack vector is inferred to be remote via the IMAP protocol. Because the execution simply results in a data leak, it does not directly enable code execution or privilege escalation, but it could aid an adversary in gathering information for future attacks. The vulnerability is not listed in CISA KEV at present.

Generated by OpenCVE AI on July 31, 2026 at 02:27 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Cyrus IMAP to version 3.12.3 or later, which contains the fix for the malformed MIME comment parsing bug.
  • If upgrading is not immediately possible, restrict authenticated users from sending MIME comments that end with a backslash or disable MIME comment parsing through server configuration to prevent the buffer over-read.
  • Apply any vendor‑supplied security controls that limit exposure of heap memory, such as configuring strict parsing flags or enabling memory‑sanitizing features if available.

Generated by OpenCVE AI on July 31, 2026 at 02:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 18 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Title cyrus-imapd: Cyrus IMAP: Information disclosure via heap exposure in MIME comment parsing
Weaknesses CWE-125
References
Metrics threat_severity

None

threat_severity

Low


Thu, 16 Jul 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

Cyrusimap Cyrus Imap
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-07-16T19:01:31.618Z

Reserved: 2026-05-18T00:00:00.000Z

Link: CVE-2026-47088

cve-icon Vulnrichment

Updated: 2026-07-16T19:01:27.907Z

cve-icon NVD

No data.

cve-icon Redhat

Severity : Low

Publid Date: 2026-07-16T00:00:00Z

Links: CVE-2026-47088 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T02:30:05Z

Weaknesses