Kopano develops an open-source groupware and collaboration platform centered on its core messaging and web-application components, serving as a self-hosted alternative to proprietary enterprise communication systems. Its observed vulnerability exposure reflects the input-handling and authentication demands of a web-facing mail and calendaring platform, with recurring weaknesses in resource exhaustion, buffer management, input validation, and cross-site scripting that are typical of application-layer services. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Kopano over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-26562CRITICAL An issue in provider/libserver/ECKrbAuth.cpp of Kopano Core <= v11.0.2.51 contains an issue which allows attackers to authenticate even if the user account or password is expired. | Apr 1, 2022 | 9.8 | 31 | NO | NO |
CVE-2019-19907CRITICAL HrAddFBBlock in libfreebusy/freebusyutil.cpp in Kopano Groupware Core before 8.7.7 allows out-of-bounds access, as demonstrated by mishandling of an array copy during parsing of IC | Dec 19, 2019 | 9.8 | 29 | NO | NO |
CVE-2021-28994HIGH kopano-ical (formerly zarafa-ical) in Kopano Groupware Core through 8.7.16, 9.x through 9.1.0, 10.x through 10.0.7, and 11.x through 11.0.1 and Zarafa 6.30.x through 7.2.x allows m | Mar 31, 2021 | 7.5 | 21 | NO | NO |
CVE-2017-11666MEDIUM Cross-site scripting (XSS) vulnerability in js/ViewerPanel.js in the file previewer plugin in Kopano WebApp versions 3.3.0 and earlier allows remote attackers to inject arbitrary w | Jul 26, 2017 | 6.1 | 20 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Kopano.
Media articles that mention a CVE ID that affects a product developed by Kopano — matched by CVE ID, not by vendor name.