Skip to content
Fencer Vulns
medium 4.7

CVE-2026-54432 json

Roundcube Webmail before 1.6.17 and 1.7.x before 1.7.2 allows Stored Cross-Site Scripting (XSS).

published 2026-07-14 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-43733

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

Summary

Roundcube Webmail before 1.6.17 and 1.7.x before 1.7.2 allows Stored Cross-Site Scripting (XSS). The issue occurs because the attachment MIME type is not properly escaped on the attachment-validation warning page.

Patch / fix

  • Roundcube Webmail 1.6.17, 1.7.2
  • roundcube Debian 12 1.6.5+dfsg-1+deb12u10
  • roundcube Debian 13 1.6.17+dfsg-0+deb13u1
  • roundcube Debian 14 1.6.17+dfsg-1

debian advisories DEBIAN-CVE-2026-54432

  • roundcubemail openSUSE Leap 16.0 1.6.20-bp160.1.1
  • roundcubemail openSUSE Tumbleweed 1.6.19-1.1

opensuse advisories openSUSE-SU-2026:22195-1openSUSE-SU-2026:12169-1

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-54432 updated cvss 4.7

roundcubemail: Roundcube Webmail: Stored Cross-Site Scripting via unescaped attachment MIME type

  • 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
3 mo ago

Exploit prediction

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

CVSS scores

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

Affected products

  • Roundcube Webmail

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.