Skip to main content
← All vulnerabilities
CVE-2026-114720

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by an IMAP command injection vulnerability.

Published
Last modified
published
Not listed in CISA KEV
Specific setups only
Fix
Fixed in 1.6.20, 1.7.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by an IMAP command injection vulnerability. A remote authenticated attacker can exploit this via CRLF sequences injected into the _flag parameter of the mail/mark action to execute arbitrary IMAP commands. Upstream fixed this in the commit “Fix IMAP command injection via CRLF in `_flag` parameter of mail/mark action”, which rejects flags containing control, whitespace and IMAP-special characters.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • Roundcube Webmail

    From 1.6.0 · fixed in 1.6.20; From 1.7.0 · fixed in 1.7.5

References 6

bugs.debian.org

GitHub · roundcube/roundcubemail

roundcube.net

FAQ

Questions about CVE-2026-114720

What does this mean?

The _flag parameter of Roundcube's mail/mark action does not strip CRLF sequences, so an attacker-supplied value can inject extra IMAP commands into the server session. The advisory describes this as IMAP command injection via CRLF in that parameter.Source: roundcube.net

Am I affected, and how do I check?

Roundcube Webmail 1.6.x before 1.6.20 and 1.7.x before 1.7.5 are affected. To check, look at the Roundcube version shown in the footer or the program/includes version file of your installation.Source: roundcube.net

What should I do about it?

Upgrade to Roundcube Webmail 1.6.20 if you run the 1.6 branch, or to 1.7.5 if you run the 1.7 branch. Both versions are listed as fixed releases.Source: roundcube.net

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data