Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain authenticated IMAP account on target server
-
DeliveryIssue ESEARCH command targeting victim's namespace
-
ExploitObserve returned UID counts and message identifiers
-
ExecutionVary search terms to enumerate folder names
-
PersistMap victim's mailbox structure
-
ImpactInfer sensitive organizational or personal information from folder naming
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication Response uniformity
|
| Exploitation Conditions | The attacker must hold a valid, authenticated IMAP account on the affected server (CVSS PR:L confirms this requirement). The ESEARCH IMAP extension must be available - it is enabled by default in Cyrus IMAP and no special configuration is required to activate it. The attack succeeds against any Cyrus IMAP version through 3.12.2 without requiring any non-default configuration. The attacker must be able to name the target account (e.g., know a victim's username or enumerate usernames via another method), but does not require any cooperation or interaction from the victim. What limits exploitation: authentication is mandatory (no unauthenticated path); only folder names and message UIDs are exposed, not message content; and in single-tenant deployments where all users are peers, the privacy impact is minimal. Meaningful exploitation is realistically constrained to multi-tenant environments where account isolation is an expected security property. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N and score of 4.3 are well-calibrated: the attack is network-reachable with low complexity but requires a valid authenticated account (PR:L), and impact is strictly limited to low confidentiality - folder names and UIDs are disclosed, but message bodies cannot be read. No EPSS score was provided in the input data, preventing quantitative exploitation probability assessment. The absence of both a CISA KEV listing and any known public POC indicates no public exploit has been identified at time of analysis. Real-world risk varies significantly by deployment context: in shared multi-tenant environments (universities, ISPs, or hosted email providers), this flaw enables meaningful privacy violations as attackers could map the mailbox structure of targeted individuals or organizations. In single-tenant or internal corporate deployments where all IMAP users are already peers, the incremental risk is substantially lower. No conflicting signals exist between the CVSS vector and the description - authentication requirement and limited impact are consistently represented. |
| Exploit ScenarioDerived | An attacker with a low-privilege authenticated account on a shared Cyrus IMAP server - such as a student on a university mail system or a customer on an ISP - issues ESEARCH commands targeting named victim accounts (e.g., user.targetname) with varied search criteria. The server returns UID lists for matching messages, confirming the existence of specific folders and the presence of messages meeting the search conditions, allowing the attacker to infer sensitive organizational structure (e.g., confirming a folder named 'legal-hold' or 'acquisition-talks' exists) without ever reading message content. No public POC has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 16, 2026
Cross-user information disclosure in Cyrus IMAP through 3.12.2 allows any authenticated IMAP user to enumerate folder names and retrieve message UIDs belonging to arbitrary other accounts via the ESEARCH command, creating a content oracle. The flaw (CWE-204, Observable Response Discrepancy) leaks mailbox structure - including folder names that may reveal sensitive organizational or personal context - without permitting reads of actual message content. No public exploit code has been identified at time of analysis, no CISA KEV listing exists, and the CVSS score of 4.3 reflects the authentication prerequisite and limited confidentiality impact, though risk is elevated in shared multi-tenant deployments such as ISPs and universities.
RemediationAI
Upgrade to Cyrus IMAP 3.12.3 or later as indicated by the vendor release notes at https://www.cyrusimap.org/3.12/imap/download/release-notes/3.12/x/3.12.3.html; the general release index at https://www.cyrusimap.org/imap/download/release-notes/index.html should be consulted for fixes applicable to other supported branches. If an immediate upgrade is not feasible, administrators can reduce exposure by restricting IMAP namespace access: configuring Cyrus IMAP's namespace settings to disable cross-user namespace access (e.g., setting altnamespace and disabling the shared or other-users namespace in imapd.conf) would prevent ESEARCH from reaching other users' mailboxes, though this may break legitimate IMAP sharing and delegation workflows. Deploying an IMAP proxy layer with strict namespace enforcement is an additional option but introduces operational complexity. Disabling ESEARCH entirely is not recommended as it would broadly degrade IMAP client performance. Note that patch version 3.12.3 is inferred from the referenced URL and has not been independently confirmed via a separate security advisory.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Cyrus IMAP is an open-source IMAP server developed by Carnegie Mellon University's Project Cyrus and widely deployed in academic, ISP, and enterprise environments. The vulnerability lies in the server's handling of the ESEARCH command (defined in RFC 4731 as a structured extension to standard IMAP SEARCH), which is enabled by default. CWE-204 (Observable Response Discrepancy) describes flaws where response differences reveal information an actor should not have access to - here, ESEARCH returns structured UID lists for messages matching the query, and the implementation fails to scope cross-namespace queries to only the requesting user's authorized mailboxes. The CPE string cpe:2.3:a:cyrusimap:cyrus_imap:*:*:*:*:*:*:*:* covers all versions through 3.12.2. Because IMAP namespaces allow addressing other users' mailboxes directly (e.g., user.victim), the ESEARCH oracle permits inference of folder existence and message presence across the entire server population without any grant of read access.
Know when Cyrus Imap gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network-accessible IMAP command requiring valid credentials (PR:L); only low confidentiality impact as folder names and UIDs are exposed but message content is not readable.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
1DescriptionCVE.org
An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is an ESEARCH cross-user content oracle. By using the ESEARCH command, an authenticated IMAP user could enumerate folder names under any account they could name. Search would return UIDs of messages matching the search, creating a content oracle (without allowing arbitrary reads of the target's content).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Cyrus Imap
View allCyrus IMAP before 3.0.3 allows remote authenticated users to write to arbitrary files via a crafted (1) SYNCAPPLY, (2) S
Unauthorized mailbox deletion in Cyrus IMAP through 3.12.2 allows any authenticated non-admin user to invoke the admin-o
Cyrus IMAP before 3.8.3 and 3.10.x before 3.10.0-rc1 allows authenticated attackers to cause unbounded memory allocation
Incorrect authorization in Cyrus IMAP through 3.12.2 allows authenticated users to bypass mailbox ACL enforcement via th
Cyrus IMAP through 3.12.2 exposes mailbox ACL data to any authenticated user via the IMAP LISTRIGHTS command, which lack
URLAUTH token forgery in Cyrus IMAP through 3.12.2 allows a network-based unauthenticated attacker to read the contents
Cyrus IMAP through version 3.12.2 fails to invalidate URLAUTH-minted URLs when the authorizer's access is subsequently r
Unauthorized mailbox access in Cyrus IMAP through 3.12.2 allows any authenticated user to read email from mailboxes they
Heap over-read in Cyrus IMAP through version 3.12.2 enables authenticated IMAP users to leak server heap memory by submi
Cyrus IMAP through version 3.12.2 contains an authorization flaw in its XAPPLEPUSHSERVICE (XAPS) command that lets authe
Same weakness CWE-204 – Observable Response Discrepancy
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
EUVD-2026-45006
GHSA-7m4j-qx5p-343w
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB