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-114721 Overview
CVE-2026-114721 is an authorization bypass vulnerability [CWE-863] in Roundcube Webmail. The flaw allows an authenticated attacker to reach actions blocked by the disabled_actions configuration by requesting them through deprecated action aliases. Roundcube's access check compared only the requested action name without resolving aliases, so a disabled action remained reachable under a different name. Upstream fixed this in versions 1.6.20 and 1.7.5 by relocating the check into rcmail::action_handler() and resolving aliases before comparison.
Critical Impact
Authenticated users can invoke actions that administrators explicitly disabled via disabled_actions, undermining a documented security hardening control in Roundcube Webmail.
Affected Products
- Roundcube Webmail versions prior to 1.6.20
- Roundcube Webmail 1.7.x versions prior to 1.7.5
- Deployments relying on the disabled_actions configuration setting for hardening
Discovery Timeline
- 2026-10-19 - Roundcube publishes security updates 1.6.20 and 1.7.5
- 2026-10-22 - CVE-2026-114721 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114721
Vulnerability Analysis
Roundcube supports an administrator-configurable disabled_actions list in config.inc.php. The list prevents specific task.action combinations from being invoked, even by authenticated users. The pre-patch enforcement logic lived in public_html/index.php and compared the request string task.action directly against the configured deny list.
Roundcube also maintains deprecated aliases for several actions to preserve backward compatibility with older URLs and bookmarks. The alias-to-canonical-action resolution occurred later in the request lifecycle, after the disabled_actions check had already passed. An authenticated attacker could therefore request a disabled action through its deprecated alias and reach the handler unimpeded.
Root Cause
The root cause is an authorization check performed against unresolved input. The deny-list comparison used the raw action name from the HTTP request, while alias normalization occurred downstream. Any action that had both a canonical name and a deprecated alias effectively had two code paths into its handler, but only one was gated by disabled_actions.
Attack Vector
Exploitation requires an authenticated Roundcube session and knowledge of the deprecated alias corresponding to the target action. The attacker submits a standard HTTP request to the Roundcube endpoint, substituting the alias for the canonical action name. The server processes the request, bypasses the deny-list comparison, resolves the alias internally, and dispatches the originally disabled action.
// Upstream fix in program/include/rcmail.php — the CSRF and disabled-action
// enforcement is moved into action_handler(), which runs AFTER alias resolution.
*/
public function action_handler()
{
// CSRF prevention
$this->request_security_check();
// we're ready, user is authenticated and the request is safe
$plugin = $this->plugins->exec_hook('ready', ['task' => $this->task, 'action' => $this->action]);
Source: Roundcube Commit cd41314
// Removed from public_html/index.php — this pre-resolution check was
// bypassable because $RCMAIL->action still held the deprecated alias.
} else {
// CSRF prevention
$RCMAIL->request_security_check();
// check access to disabled actions
$disabled_actions = (array) $RCMAIL->config->get('disabled_actions');
if (in_array($RCMAIL->task . '.' . ($RCMAIL->action ?: 'index'), $disabled_actions)) {
rcube::raise_error([
'code' => 404,
'message' => 'Action disabled',
], true, true);
}
}
$RCMAIL->action_handler();
Source: Roundcube Commit cd41314
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-114721
Indicators of Compromise
- HTTP requests to Roundcube endpoints using deprecated _action parameter values that correspond to actions enumerated in the server's disabled_actions configuration.
- Successful HTTP 200 responses to actions that administrators expect to return HTTP 404 "Action disabled" errors.
- Unexpected authenticated activity against features intentionally restricted via disabled_actions.
Detection Strategies
- Inventory the exact task.action entries configured in each Roundcube instance's disabled_actions and build a mapping of their deprecated aliases from the Roundcube source tree.
- Alert on web server or reverse proxy access logs that show requests containing those alias values paired with authenticated session cookies.
- Compare the request-time _action parameter against the dispatched handler recorded in Roundcube debug logs to identify alias-based access patterns.
Monitoring Recommendations
- Enable Roundcube's debug logging for the duration of patch rollout and review logs/errors.log and logs/console for anomalous action dispatches.
- Ingest reverse-proxy access logs into a centralized logging platform and build searches for Roundcube endpoints that reference known alias strings.
- Track authenticated user sessions that exhibit abnormal breadth of action invocations relative to baseline user behavior.
How to Mitigate CVE-2026-114721
Immediate Actions Required
- Upgrade Roundcube Webmail to version 1.6.20 or 1.7.5, as described in the Roundcube Security Updates Announcement.
- Audit the disabled_actions configuration in config/config.inc.php and confirm that the actions you intended to disable are not reachable after upgrade.
- Review web server access logs for prior requests that may have invoked disabled actions through deprecated aliases.
Patch Information
Roundcube addressed the issue in commits cd41314 and e7c512a, shipped in Roundcube Release v1.6.20 and Roundcube Release v1.7.5. The fix moves both the CSRF check and the disabled_actions comparison into rcmail::action_handler(), which executes after alias resolution. Debian users should also consult Debian Bug Report #1151279 for distribution packaging status.
Workarounds
- If immediate patching is not possible, extend the disabled_actions list to include every known deprecated alias for the actions you intend to restrict.
- Restrict Roundcube access to trusted networks or require VPN authentication to reduce the pool of users who could abuse the bypass.
- Enforce multi-factor authentication for Roundcube logins so that credential theft alone does not permit exploitation of this authenticated flaw.
# config/config.inc.php — temporary hardening before upgrade
# Explicitly list both canonical actions and their deprecated aliases.
$config['disabled_actions'] = [
'mail.compose', // canonical action to restrict
'mail.send', // additional canonical action
// Add every deprecated alias that resolves to the restricted actions
// by cross-referencing the Roundcube source tree for your version.
];
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

