Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114732 Overview
CVE-2026-114732 is an improper authentication vulnerability in Roundcube Webmail affecting multi-host installations. The flaw resides in the rcube_user::query() function, which resolves alias logins against identity records without qualifying the lookup by Internet Message Access Protocol (IMAP) host. An attacker authenticating with an alias address can be matched to a user account belonging to a different IMAP host, enabling cross-tenant account resolution. The vulnerability is categorized under [CWE-288] Authentication Bypass Using an Alternate Path or Channel. Roundcube addressed the issue in versions 1.6.20 and 1.7.5.
Critical Impact
Authenticated users on shared Roundcube deployments can be resolved to accounts on different IMAP hosts, breaking tenant isolation and exposing mailbox contents of unrelated users.
Affected Products
- Roundcube Webmail versions prior to 1.6.20
- Roundcube Webmail 1.7.x versions prior to 1.7.5
- Multi-host Roundcube installations serving multiple IMAP backends
Discovery Timeline
- 2026-10-19 - Roundcube publishes security updates 1.6.20 and 1.7.5
- 2026-10-22 - CVE-2026-114732 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114732
Vulnerability Analysis
Roundcube Webmail supports alias logins by resolving the provided address against the identities table. In multi-host deployments, a single Roundcube instance brokers authentication for multiple IMAP servers, each serving distinct user populations. The pre-patch SQL query joined the users and identities tables but filtered only on the email column of identities. The lookup ignored the IMAP mail_host associated with the submitted credentials. An alias record matching an address registered under a different mail_host could therefore satisfy the query and return a foreign user record.
Successful exploitation grants session context tied to the resolved user, including mailbox access and identity metadata. The attacker still needs valid credentials to authenticate against the IMAP backend, which raises exploitation complexity but does not eliminate risk in shared alias namespaces.
Root Cause
The root cause is a missing scoping predicate in the identity resolution query inside program/lib/Roundcube/rcube_user.php. The SELECT statement filtered identities on email alone, omitting the u.mail_host constraint required to bind the lookup to a specific IMAP backend. In single-host deployments this had no effect, but multi-host installations collapsed into a shared alias namespace across tenants.
Attack Vector
Exploitation requires network access to a vulnerable Roundcube login page and knowledge of an alias address shared across IMAP backends. The attacker submits the alias and valid credentials; the server resolves the identity to the first matching user regardless of mail_host affiliation. No user interaction is required beyond standard login.
// Patch for program/lib/Roundcube/rcube_user.php
// Source: https://github.com/roundcube/roundcubemail/commit/453c413d6851cf603bebdb15e58381f5ef9b8094
$sql_result = $dbh->limitquery('SELECT u.*'
. ' FROM ' . $dbh->table_name('users', true) . ' u'
. ' JOIN ' . $dbh->table_name('identities', true) . ' i ON (i.`user_id` = u.`user_id`)'
- . ' WHERE `email` = ? AND `del` <> 1',
- 0, 1, $user
+ . ' WHERE u.`mail_host` = ? AND i.`email` = ? AND i.`del` <> 1',
+ 0, 1, $host, $user
);
$sql_arr = $dbh->fetch_assoc($sql_result);
The fix adds the u.mail_host = ? predicate and binds the current IMAP host as the first parameter, qualifying the identity lookup to the correct backend. Source: Roundcube Commit 453c413.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114732
Indicators of Compromise
- Successful Roundcube login events where the resolved user_id maps to a mail_host different from the IMAP server used for authentication.
- Session records showing mailbox access patterns inconsistent with the user's historical IMAP backend assignment.
- Duplicate alias addresses present across identities rows tied to distinct mail_host values in the users table.
Detection Strategies
- Audit the Roundcube database with a query joining users and identities to identify alias email values shared across multiple mail_host entries.
- Enable Roundcube debug logging (per_user_logging) and inspect userlogins.log for logins where the alias resolution differs from the submitted IMAP host.
- Correlate web server access logs with IMAP server logs to flag sessions where the Roundcube-resolved user does not match the authenticating IMAP backend.
Monitoring Recommendations
- Centralize Roundcube, IMAP, and web server logs into a SIEM and alert on cross-host account resolutions.
- Monitor /program/ endpoints for authentication anomalies, including repeated logins with the same alias from different source addresses.
- Track changes to the identities table to detect alias additions that overlap tenants.
How to Mitigate CVE-2026-114732
Immediate Actions Required
- Upgrade Roundcube Webmail to version 1.6.20 or 1.7.5 immediately on all multi-host installations.
- Inventory the identities table for duplicate alias addresses spanning multiple mail_host values and remove or reassign conflicts.
- Invalidate active sessions after patching to force re-authentication through the fixed code path.
Patch Information
Roundcube released fixes on 2026-10-19 in versions 1.6.20 and 1.7.5. The patches modify program/lib/Roundcube/rcube_user.php to qualify the identity lookup by mail_host. Reference the Roundcube Security Updates Announcement, Roundcube Release 1.6.20, and Roundcube Release 1.7.5. Debian packaging status is tracked in Debian Bug Report #1151279.
Workarounds
- Deploy separate Roundcube instances per IMAP host to eliminate the shared alias namespace until patching is complete.
- Enforce unique alias addresses across tenants by database constraint or administrative review.
- Restrict Roundcube login to authenticated reverse proxies that bind sessions to a specific IMAP backend.
# Audit for cross-host alias collisions in the Roundcube database
mysql -u roundcube -p roundcubemail -e \
"SELECT i.email, COUNT(DISTINCT u.mail_host) AS host_count \
FROM identities i JOIN users u ON i.user_id = u.user_id \
WHERE i.del <> 1 \
GROUP BY i.email HAVING host_count > 1;"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

