CVE-2025-68460 json
Roundcube Webmail before 1.5.12 and 1.6 before 1.6.12 is prone to a information disclosure vulnerability in the HTML style sanitizer.
published 2025-12-18 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-204036
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Roundcube Webmail before 1.5.12 and 1.6 before 1.6.12 is prone to a information disclosure vulnerability in the HTML style sanitizer.
Patch / fix
- Roundcube Webmail 1.5.12, 1.6.12
- roundcube Debian 12 1.6.5+dfsg-1+deb12u6
- roundcube Debian 13 1.6.12+dfsg-0+deb13u1
- roundcube Debian 14 1.6.12+dfsg-1
debian advisories DEBIAN-CVE-2025-68460
- roundcubemail openSUSE Leap 16.0 1.6.13-bp160.1.1
opensuse advisories openSUSE-SU-2026:20323-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-2025-68460 updated cvss 5.4
roundcubemail: Roundcube Webmail: Information Disclosure via HTML Style Sanitizer
-
Red Hat All currently supported Red Hat productsnot 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
- yes
- Technical impact
- partial
- Assessed
- 10 mo ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 21% 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 |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Roundcube Webmail
Classification
- Weakness
-
- CWE-116 Improper Encoding or Escaping of Output
References
Sources
- CVE List CVE-2025-68460
- NVD CVE-2025-68460
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.