Skip to content
Fencer Vulns
low 3.1

CVE-2026-35538 json

Roundcube Webmail: Unsanitized IMAP SEARCH command arguments

published 2026-04-03 7 mo ago modified 2026-07-24 3 mo ago also GHSA-8jr8-v43g-5c57 , EUVD-2026-18579

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

An issue was discovered in Roundcube Webmail before 1.5.14 and 1.6.14. Unsanitized IMAP SEARCH command arguments could lead to IMAP injection or CSRF bypass during mail search.

Patch / fix

  • packagist roundcube/roundcubemail 1.7-rc5
  • Roundcube Webmail 1.5.14, 1.6.14
  • roundcube Debian 12 1.6.5+dfsg-1+deb12u8
  • roundcube Debian 13 1.6.15+dfsg-0+deb13u1
  • roundcube Debian 14 1.6.14+dfsg-1

debian advisories DEBIAN-CVE-2026-35538

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-35538 updated cvss 4.6

Roundcube Webmail: Roundcube Webmail: IMAP injection and CSRF bypass due to unsanitized search arguments

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist roundcube/roundcubemail
>=1.7-beta, <1.7-rc5
1.7-rc5

Affected products

  • Roundcube Webmail

Classification

Weakness
  • CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.