Skip to content
Fencer Vulns
high 7.2

CVE-2026-48848 json

Roundcube Webmail 1.6.x before 1.6.16 and 1.7.x before 1.7 has insufficient HTML sanitization that could lead to Cascading Style Sheets (CS…

published 2026-05-25 5 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-31727

cvss
7.2
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 33%
public exploits
0
none known

Summary

Roundcube Webmail 1.6.x before 1.6.16 and 1.7.x before 1.7 has insufficient HTML sanitization that could lead to Cascading Style Sheets (CSS) injection via an SVG document that has an animate element with the attributeName attribute.

Patch / fix

  • Roundcube Webmail 1.6.16, 1.7.1
  • roundcube Debian 12 1.6.5+dfsg-1+deb12u9
  • roundcube Debian 13 1.6.16+dfsg-0+deb13u1
  • roundcube Debian 14 1.6.16+dfsg-1

debian advisories DEBIAN-CVE-2026-48848

  • roundcubemail openSUSE Tumbleweed 1.6.16-2.1

opensuse advisories openSUSE-SU-2026:10869-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-48848 updated cvss 7.2

roundcubemail: CSS injection via an SVG document that has an animate element with the attributeName attribute

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

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.