en
Severity across 2 analyzed records
A short verification protects source data and prevents automated AI requests.
| CVE | Exploitation status | Fix | Affected product | Published | Severity |
|---|---|---|---|---|---|
CVE-2026-73576CVE-2026-73576 | Exploitation statusNot known exploited | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityMedium |
CVE-2026-73575CVE-2026-73575 | Exploitation statusNot known exploited | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityLow |
CVE-2026-73574CVE-2026-73574 | Exploitation statusNot known exploited | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityLow |
CVE-2026-73573CVE-2026-73573 | Exploitation statusNot known exploited | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityLow |
CVE-2026-73572CVE-2026-73572 | Exploitation statusNot known exploited | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityMedium |
CVE-2026-73571CVE-2026-73571 | Exploitation statusNot known exploited | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityLow |
CVE-2026-73570CVE-2026-73570 | Exploitation statusKEV | FixYes | Affected productCollaboration | Published08/13/2026 | SeverityHigh |
CVE-2026-33373CVE-2026-33373 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published03/30/2026 | SeverityHigh |
CVE-2026-33368CVE-2026-33368 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published03/20/2026 | SeverityMedium |
CVE-2026-33369CVE-2026-33369 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published03/20/2026 | SeverityMedium |
CVE-2026-33371CVE-2026-33371 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published03/20/2026 | SeverityMedium |
CVE-2026-33372CVE-2026-33372 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published03/20/2026 | SeverityMedium |
CVE-2026-33370CVE-2026-33370 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published03/20/2026 | SeverityMedium |
CVE-2025-66376CVE-2025-66376 | Exploitation statusKEV | FixYes | Affected productCollaboration | Published01/05/2026 | SeverityHigh |
CVE-2025-68645CVE-2025-68645 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published12/22/2025 | SeverityHigh |
CVE-2025-48700CVE-2025-48700 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published06/23/2025 | SeverityMedium |
CVE-2024-45516CVE-2024-45516 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published05/14/2025 | SeverityMedium |
CVE-2025-32354CVE-2025-32354 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published04/29/2025 | SeverityHigh |
CVE-2025-27915CVE-2025-27915 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published03/12/2025 | SeverityMedium |
CVE-2025-25064CVE-2025-25064 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published02/03/2025 | SeverityHigh |
CVE-2025-25065CVE-2025-25065 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published02/03/2025 | SeverityMedium |
CVE-2024-54663CVE-2024-54663 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published12/19/2024 | SeverityHigh |
CVE-2024-45517CVE-2024-45517 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/21/2024 | SeverityMedium |
CVE-2024-45514CVE-2024-45514 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/21/2024 | SeverityMedium |
CVE-2024-45513CVE-2024-45513 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/21/2024 | SeverityMedium |
CVE-2024-45512CVE-2024-45512 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/21/2024 | SeverityMedium |
CVE-2024-45194CVE-2024-45194 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/21/2024 | SeverityMedium |
CVE-2024-45510CVE-2024-45510 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/20/2024 | SeverityMedium |
CVE-2024-45511CVE-2024-45511 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/20/2024 | SeverityMedium |
CVE-2024-50599CVE-2024-50599 | Exploitation statusNot known exploited | FixNot confirmed | Affected productNot confirmed | Published11/07/2024 | SeverityMedium |
CVE-2024-45519CVE-2024-45519 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published10/02/2024 | SeverityCritical |
CVE-2023-37580CVE-2023-37580 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published07/31/2023 | SeverityMedium |
CVE-2023-34192CVE-2023-34192 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published07/06/2023 | SeverityCritical |
CVE-2022-3569CVE-2022-3569 | Exploitation statusPublic exploit | FixNot confirmed | Affected productZimbra Collaboration Suite (ZCS) | Published10/17/2022 | SeverityHigh |
CVE-2022-41352CVE-2022-41352 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published09/26/2022 | SeverityCritical |
CVE-2022-37393Zimbra zmslapd arbitrary module load | Exploitation statusNot confirmed | FixNot confirmed | Affected productZimbra Server | Published08/16/2022 | SeverityUnknown |
CVE-2022-37042CVE-2022-37042 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published08/11/2022 | SeverityCritical |
CVE-2022-27926CVE-2022-27926 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published04/20/2022 | SeverityMedium |
CVE-2022-27925CVE-2022-27925 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published04/20/2022 | SeverityHigh |
CVE-2022-27924CVE-2022-27924 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published04/20/2022 | SeverityHigh |
CVE-2022-24682CVE-2022-24682 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published02/09/2022 | SeverityMedium |
CVE-2020-18985CVE-2020-18985 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/15/2021 | SeverityUnknown |
CVE-2020-18984CVE-2020-18984 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/15/2021 | SeverityUnknown |
CVE-2020-13653CVE-2020-13653 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/02/2020 | SeverityUnknown |
CVE-2020-12846CVE-2020-12846 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published06/03/2020 | SeverityUnknown |
CVE-2020-8633CVE-2020-8633 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/18/2020 | SeverityUnknown |
CVE-2020-7796CVE-2020-7796 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published02/18/2020 | SeverityCritical |
CVE-2014-8563CVE-2014-8563 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/27/2020 | SeverityUnknown |
CVE-2015-2249CVE-2015-2249 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/27/2020 | SeverityUnknown |
CVE-2014-5500CVE-2014-5500 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/27/2020 | SeverityUnknown |
CVE-2019-11318CVE-2019-11318 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/27/2020 | SeverityUnknown |
CVE-2015-2230CVE-2015-2230 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2019 | SeverityUnknown |
CVE-2015-7609CVE-2015-7609 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2019 | SeverityUnknown |
CVE-2018-10948CVE-2018-10948 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2019 | SeverityUnknown |
CVE-2018-14425CVE-2018-14425 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2019 | SeverityUnknown |
CVE-2018-15131CVE-2018-15131 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2019 | SeverityUnknown |
CVE-2018-18631CVE-2018-18631 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/29/2019 | SeverityUnknown |
CVE-2018-14013CVE-2018-14013 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/29/2019 | SeverityUnknown |
CVE-2019-6981CVE-2019-6981 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/29/2019 | SeverityUnknown |
CVE-2018-20160CVE-2018-20160 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/29/2019 | SeverityUnknown |
CVE-2019-6980CVE-2019-6980 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/29/2019 | SeverityUnknown |
CVE-2019-9670CVE-2019-9670 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published05/29/2019 | SeverityCritical |
CVE-2019-9621CVE-2019-9621 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published04/30/2019 | SeverityHigh |
CVE-2018-17938CVE-2018-17938 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published10/03/2018 | SeverityUnknown |
CVE-2015-7610CVE-2015-7610 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2018 | SeverityUnknown |
CVE-2018-10939CVE-2018-10939 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/30/2018 | SeverityUnknown |
CVE-2018-10951CVE-2018-10951 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/10/2018 | SeverityUnknown |
CVE-2018-10949CVE-2018-10949 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/10/2018 | SeverityUnknown |
CVE-2018-10950CVE-2018-10950 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/10/2018 | SeverityUnknown |
CVE-2018-6882CVE-2018-6882 | Exploitation statusKEV | FixNot confirmed | Affected productNot confirmed | Published03/27/2018 | SeverityMedium |
CVE-2017-17703CVE-2017-17703 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/04/2018 | SeverityUnknown |
CVE-2017-8783CVE-2017-8783 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/04/2018 | SeverityUnknown |
CVE-2017-7288CVE-2017-7288 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/23/2017 | SeverityUnknown |
CVE-2017-6813CVE-2017-6813 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/23/2017 | SeverityUnknown |
CVE-2017-6821CVE-2017-6821 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/23/2017 | SeverityUnknown |
CVE-2016-3403CVE-2016-3403 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/17/2017 | SeverityUnknown |
CVE-2016-9924CVE-2016-9924 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/29/2017 | SeverityUnknown |
CVE-2016-3406CVE-2016-3406 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3410CVE-2016-3410 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3402CVE-2016-3402 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3414CVE-2016-3414 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3412CVE-2016-3412 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3409CVE-2016-3409 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3413CVE-2016-3413 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3999CVE-2016-3999 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3408CVE-2016-3408 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3404CVE-2016-3404 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3411CVE-2016-3411 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-4019CVE-2016-4019 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3415CVE-2016-3415 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3405CVE-2016-3405 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3407CVE-2016-3407 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2016-3401CVE-2016-3401 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/18/2017 | SeverityUnknown |
CVE-2013-7091CVE-2013-7091 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published12/13/2013 | SeverityUnknown |
CVE-2013-5119CVE-2013-5119 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published09/23/2013 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
.svg){kind=icon}
