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-114724 Overview
CVE-2026-114724 is a PHP object injection vulnerability in Roundcube Webmail affecting versions before 1.6.20 and 1.7.x before 1.7.5. The flaw resides in rcube_session::unserialize(), where session keys prefixed with ! were treated as having no value. This caused the reconstructed serialized string to emit a key without a corresponding value, desynchronizing the parser so that subsequent session data was interpreted as a serialized PHP value. An attacker able to influence stored session data can trigger object instantiation through this primitive, enabling exploitation chains dependent on available gadget classes. The issue is tracked under CWE-502: Deserialization of Untrusted Data.
Critical Impact
Attackers who can influence stored session data obtain a PHP object injection primitive, which can lead to arbitrary code execution when exploitable gadget chains exist in the application context.
Affected Products
- Roundcube Webmail versions prior to 1.6.20
- Roundcube Webmail 1.7.x versions prior to 1.7.5
- Downstream distributions packaging vulnerable Roundcube releases (see Debian Bug Report #1151279)
Discovery Timeline
- 2026-10-19 - Roundcube publishes security releases 1.6.20 and 1.7.5 (Roundcube Security Updates Announcement)
- 2026-10-22 - CVE-2026-114724 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114724
Vulnerability Analysis
Roundcube's custom session serializer, implemented in program/lib/Roundcube/rcube_session.php, walks the stored session string and reconstructs a PHP-serialized representation that is later passed to unserialize(). When the parser encountered a key beginning with the ! character, it set $has_value = false, advanced the pointer past the marker, and emitted the key without the paired value field. The remainder of the input buffer was then re-aligned against incorrect parser state, causing bytes that should have been treated as a key or structural data to be consumed as a serialized value. This yields a controllable object injection primitive against the PHP unserialize() call that consumes the reconstructed string.
Root Cause
The root cause is unsafe handling of a legacy sentinel character inside a hand-written serializer. The ! prefix was interpreted as a parser directive rather than being rejected, breaking the invariant that every emitted key is followed by its corresponding value. Because the output of rcube_session::unserialize() feeds directly into PHP's native deserializer, the desynchronization promotes attacker-controlled bytes into a serialized object payload [CWE-502].
Attack Vector
Exploitation requires the attacker to influence stored session data for the targeted Roundcube user, which under default deployments is accessible through the local session storage backend. Successful exploitation results in object instantiation under the Roundcube process context, enabling confidentiality, integrity, and availability impact when suitable gadget chains are present.
// Source: https://github.com/roundcube/roundcubemail/commit/833770d3d3c35cfde74cc2614d368f25a75b6f99
// Security patch in program/lib/Roundcube/rcube_session.php
break 2;
if ($str[$p] == '!') {
- $p++;
- $has_value = false;
- }
- else {
- $has_value = true;
+ throw new Exception('Unsupported value');
}
$name = substr($str, $p, $q - $p);
$q++;
$serialized .= 's:' . strlen($name) . ':"' . $name . '";';
- if ($has_value) {
+ // @phpstan-ignore-next-line
+ if (true) {
for (;;) {
$p = $q;
switch (strtolower($str[$q])) {
The patch removes the !-prefix branch entirely and raises an exception when such a key is encountered, eliminating the desynchronization path. A parallel fix was committed for the 1.7.x branch in Roundcube Commit 93284f3.
Detection Methods for CVE-2026-114724
Indicators of Compromise
- Session records in the configured Roundcube session store containing keys beginning with the ! character.
- PHP error log entries referencing rcube_session::unserialize(), unserialize(), or __wakeup/__destruct failures tied to the webmail PHP-FPM pool.
- Unexpected child processes (for example sh, php, curl) spawned by the web server or PHP-FPM worker that services Roundcube.
Detection Strategies
- Query the backing session store (database, Redis, Memcached, or filesystem) for any serialized session payload containing a !-prefixed key and treat matches as suspicious.
- Compare the installed Roundcube version against the fixed releases 1.6.20 and 1.7.5; any lower minor on the 1.6 or 1.7 branches is vulnerable.
- Correlate authentication events with subsequent anomalous process execution on the webmail host to catch post-exploitation gadget triggering.
Monitoring Recommendations
- Enable PHP error and exception logging for the Roundcube virtual host and forward entries to a central log platform for review.
- Monitor web server process trees for new child processes originating from the Roundcube document root.
- Audit write access to the session storage backend; only the Roundcube application account should be able to insert or modify session rows.
How to Mitigate CVE-2026-114724
Immediate Actions Required
- Upgrade Roundcube Webmail to 1.6.20 on the 1.6 branch or 1.7.5 on the 1.7 branch without delay.
- Invalidate all existing sessions after upgrade so that any attacker-planted !-prefixed keys are purged from storage.
- Review access controls on the session storage backend to confirm no untrusted process can write session records.
Patch Information
The upstream fix rejects !-prefixed keys by throwing an exception in rcube_session::unserialize(). The relevant commits are Roundcube Commit 833770d for the main branch and Roundcube Commit 93284f3 for the 1.7.x branch. Release artifacts are available at Roundcube Release 1.6.20 and Roundcube Release 1.7.5. Debian users should track the status in Debian Bug Report #1151279.
Workarounds
- If immediate patching is not possible, restrict network and operating-system level access to the Roundcube session store so only the webmail PHP process can write to it.
- Enforce strong authentication and rate limiting on Roundcube login endpoints to reduce the attacker's ability to establish a session for payload planting.
- Scan existing session storage for !-prefixed keys and delete offending records as a temporary containment measure.
# Verify Roundcube version and confirm the fix is deployed
grep -R "RCMAIL_VERSION" /var/www/roundcube/program/include/ | head
# Example: search a filesystem-based session store for !-prefixed keys
grep -rlE '(^|\|)![A-Za-z0-9_]+\|' /var/lib/php/sessions/ 2>/dev/null
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

