Webmail
Roundcube- Product type
- Other
- Catalog vulnerabilities
- 107
Severity across 38 analyzed records
en
Verify to analyze this security profile
As of 09/29/2026, within CyStack's analyzed data, Webmail has 16 security vulnerabilities published in the last 90 days. Of these, 5 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Webmail and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-75010 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-75007 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-75006 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-75004 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-75003 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-75002 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityHigh |
CVE-2026-75000 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-74999 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-74998 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityHigh |
CVE-2026-74997 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityHigh |
CVE-2026-54432 | Exploitation statusNot known exploited | FixYes | Published07/14/2026 | SeverityMedium |
CVE-2026-54433 | Exploitation statusNot known exploited | FixYes | Published07/14/2026 | SeverityHigh |
CVE-2026-62644 | Exploitation statusNot known exploited | FixYes | Published07/14/2026 | SeverityMedium |
CVE-2026-62643 | Exploitation statusNot known exploited | FixYes | Published07/14/2026 | SeverityHigh |
CVE-2026-62642 | Exploitation statusNot known exploited | FixYes | Published07/14/2026 | SeverityMedium |
CVE-2026-62641 | Exploitation statusNot known exploited | FixYes | Published07/14/2026 | SeverityMedium |
CVE-2026-9818 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2026 | SeverityUnknown |
CVE-2026-48849 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-48848 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityHigh |
CVE-2026-48847 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityLow |
CVE-2026-48846 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-48845 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-48844 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityHigh |
CVE-2026-48843 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityHigh |
CVE-2026-48842 | Exploitation statusNot known exploited | FixYes | Published05/25/2026 | SeverityHigh |
CVE-2026-35545 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35544 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35543 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35542 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35541 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35540 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35539 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityMedium |
CVE-2026-35538 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityLow |
CVE-2026-35537 | Exploitation statusNot known exploited | FixYes | Published04/03/2026 | SeverityLow |
CVE-2026-26079 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityMedium |
CVE-2026-25916 | Exploitation statusNot known exploited | FixYes | Published02/09/2026 | SeverityMedium |
CVE-2025-68461 | Exploitation statusKEV | FixYes | Published12/18/2025 | SeverityHigh |
CVE-2025-68460 | Exploitation statusNot known exploited | FixYes | Published12/18/2025 | SeverityHigh |
CVE-2025-49113 | Exploitation statusKEV | FixYes | Published06/02/2025 | SeverityCritical |
CVE-2024-57004 | Exploitation statusPublic exploit | FixNot confirmed | Published02/03/2025 | SeverityMedium |
CVE-2024-42009 | Exploitation statusKEV | FixNot confirmed | Published08/05/2024 | SeverityCritical |
CVE-2024-42008 | Exploitation statusNot known exploited | FixNot confirmed | Published08/05/2024 | SeverityCritical |
CVE-2024-37385 | Exploitation statusNot known exploited | FixNot confirmed | Published06/07/2024 | SeverityCritical |
CVE-2024-37384 | Exploitation statusNot known exploited | FixNot confirmed | Published06/07/2024 | SeverityMedium |
CVE-2024-37383 | Exploitation statusKEV | FixNot confirmed | Published06/07/2024 | SeverityMedium |
CVE-2023-47272 | Exploitation statusNot confirmed | FixNot confirmed | Published11/05/2023 | SeverityMedium |
CVE-2023-5631Stored XSS vulnerability in Roundcube | Exploitation statusKEV | FixYes | Published10/18/2023 | SeverityMedium |
CVE-2023-43770 | Exploitation statusKEV | FixNot confirmed | Published09/22/2023 | SeverityMedium |
CVE-2021-44025 | Exploitation statusNot confirmed | FixNot confirmed | Published11/19/2021 | SeverityUnknown |
CVE-2021-44026 | Exploitation statusKEV | FixNot confirmed | Published11/19/2021 | SeverityCritical |
CVE-2020-18671 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2021 | SeverityUnknown |
CVE-2020-18670 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2021 | SeverityUnknown |
CVE-2021-26925 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-35730 | Exploitation statusKEV | FixNot confirmed | Published12/28/2020 | SeverityMedium |
CVE-2020-16145 | Exploitation statusNot confirmed | FixYes | Published08/12/2020 | SeverityUnknown |
CVE-2020-15562 | Exploitation statusNot confirmed | FixNot confirmed | Published07/06/2020 | SeverityUnknown |
CVE-2020-13964 | Exploitation statusNot confirmed | FixNot confirmed | Published06/09/2020 | SeverityUnknown |
CVE-2020-13965 | Exploitation statusKEV | FixNot confirmed | Published06/09/2020 | SeverityMedium |
CVE-2020-12640 | Exploitation statusNot confirmed | FixNot confirmed | Published05/04/2020 | SeverityUnknown |
CVE-2020-12641 | Exploitation statusKEV | FixNot confirmed | Published05/04/2020 | SeverityCritical |
CVE-2020-12625 | Exploitation statusNot confirmed | FixNot confirmed | Published05/04/2020 | SeverityUnknown |
CVE-2020-12626 | Exploitation statusNot confirmed | FixNot confirmed | Published05/04/2020 | SeverityUnknown |
CVE-2019-15237 | Exploitation statusNot confirmed | FixNot confirmed | Published08/20/2019 | SeverityUnknown |
CVE-2019-10740 | Exploitation statusNot confirmed | FixNot confirmed | Published04/07/2019 | SeverityUnknown |
CVE-2018-19206 | Exploitation statusNot confirmed | FixNot confirmed | Published11/12/2018 | SeverityUnknown |
CVE-2018-19205 | Exploitation statusNot confirmed | FixNot confirmed | Published11/12/2018 | SeverityUnknown |
CVE-2017-17688 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2018 | SeverityUnknown |
CVE-2018-9846 | Exploitation statusNot confirmed | FixNot confirmed | Published04/07/2018 | SeverityUnknown |
CVE-2018-1000071 | Exploitation statusNot confirmed | FixNot confirmed | Published03/13/2018 | SeverityUnknown |
CVE-2017-16651 | Exploitation statusKEV | FixNot confirmed | Published11/09/2017 | SeverityHigh |
CVE-2015-5382 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2017 | SeverityUnknown |
CVE-2015-5383 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2017 | SeverityUnknown |
CVE-2015-5381 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2017 | SeverityUnknown |
CVE-2017-8114 | Exploitation statusNot confirmed | FixNot confirmed | Published04/29/2017 | SeverityUnknown |
CVE-2015-8864 | Exploitation statusNot confirmed | FixNot confirmed | Published04/13/2017 | SeverityUnknown |
CVE-2016-4068 | Exploitation statusNot confirmed | FixNot confirmed | Published04/13/2017 | SeverityUnknown |
CVE-2017-6820 | Exploitation statusNot confirmed | FixNot confirmed | Published03/12/2017 | SeverityUnknown |
CVE-2015-2181 | Exploitation statusNot confirmed | FixNot confirmed | Published01/30/2017 | SeverityUnknown |
CVE-2015-2180 | Exploitation statusNot confirmed | FixNot confirmed | Published01/30/2017 | SeverityUnknown |
CVE-2016-4552 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2016 | SeverityUnknown |
CVE-2016-9920 | Exploitation statusNot confirmed | FixNot confirmed | Published12/08/2016 | SeverityUnknown |
CVE-2016-4069 | Exploitation statusNot confirmed | FixNot confirmed | Published08/25/2016 | SeverityUnknown |
CVE-2015-8793 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2016 | SeverityUnknown |
CVE-2015-8105 | Exploitation statusNot confirmed | FixNot confirmed | Published11/10/2015 | SeverityUnknown |
CVE-2015-1433 | Exploitation statusNot confirmed | FixNot confirmed | Published02/03/2015 | SeverityUnknown |
CVE-2014-9587 | Exploitation statusNot confirmed | FixNot confirmed | Published01/15/2015 | SeverityUnknown |
CVE-2013-1904 | Exploitation statusNot confirmed | FixNot confirmed | Published02/08/2014 | SeverityUnknown |
CVE-2013-6172 | Exploitation statusNot confirmed | FixNot confirmed | Published11/05/2013 | SeverityUnknown |
CVE-2013-5646 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2013 | SeverityUnknown |
CVE-2013-5645 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2013 | SeverityUnknown |
CVE-2012-6121 | Exploitation statusNot confirmed | FixNot confirmed | Published02/24/2013 | SeverityUnknown |
CVE-2012-3508 | Exploitation statusNot confirmed | FixNot confirmed | Published08/25/2012 | SeverityUnknown |
CVE-2012-3507 | Exploitation statusNot confirmed | FixNot confirmed | Published08/25/2012 | SeverityUnknown |
CVE-2012-4668 | Exploitation statusNot confirmed | FixNot confirmed | Published08/25/2012 | SeverityUnknown |
CVE-2012-1253 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2012 | SeverityUnknown |
CVE-2011-4078 | Exploitation statusNot confirmed | FixNot confirmed | Published11/03/2011 | SeverityUnknown |
CVE-2011-2937 | Exploitation statusNot confirmed | FixNot confirmed | Published09/21/2011 | SeverityUnknown |
CVE-2011-1491 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2011 | SeverityUnknown |
CVE-2011-1492 | Exploitation statusNot confirmed | FixNot confirmed | Published04/08/2011 | SeverityUnknown |
CVE-2010-0464 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2010 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan