CVE-2026-74999 json
In Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3, the "Add to address book" action was subject to stored XSS.
published 2mo ago modified 2mo ago also EUVD-2026-60166
- cvss
- 5.4
- 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 17%
- public exploits
- 0
- none known
Summary
In Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3, the "Add to address book" action was subject to stored XSS.
Patch / fix
- Roundcube Webmail 1.6.18, 1.7.3
- roundcube Debian 12 1.6.5+dfsg-1+deb12u11
- roundcube Debian 13 1.6.18+dfsg-0+deb13u1
- roundcube Debian 14 1.6.18+dfsg-1
debian advisories DEBIAN-CVE-2026-74999
- 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
Is CVE-2026-74999 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/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
-
github.com
/roundcube/roundcubemail/commit/32f20c6bfd12dff9cfb6880ae303e740f0804fe8
patch
-
github.com
/roundcube/roundcubemail/commit/2d2a9604a820ee279c9ffcfe856b9b93a93995a8
patch
-
roundcube.net
/news/2026/08/09/security-updates-1.6.18-and-1.7.3
vendor-advisory
-
github.com
/roundcube/roundcubemail/releases/tag/1.6.18
release-notes
-
github.com
/roundcube/roundcubemail/releases/tag/1.7.3
release-notes
Sources
- CVE List CVE-2026-74999
- NVD CVE-2026-74999
Fencer Intel 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.