.svg){kind=icon}
DiskStation Manager (DSM)
Synology
- Product type
- Other
- Catalog vulnerabilities
- 72
Severity across 72 analyzed records
- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Verify to analyze this security profile
As of 09/19/2026, within CyStack's analyzed data, DiskStation Manager (DSM) has 19 security vulnerabilities published in the last 90 days. Of these, 6 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 DiskStation Manager (DSM) and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-40539 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityHigh |
CVE-2026-40538 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityLow |
CVE-2026-40535 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40533 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40537 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40536 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40534 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40532 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40531 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-4036 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-40530 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityHigh |
CVE-2026-13683 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityLow |
CVE-2026-13623 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-13666 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityLow |
CVE-2026-6205 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityHigh |
CVE-2026-13673 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityHigh |
CVE-2026-13635 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityMedium |
CVE-2026-13639 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityCritical |
CVE-2026-13684 | Exploitation statusNot known exploited | FixYes | Published09/18/2026 | SeverityCritical |
CVE-2025-13392 | Exploitation statusNot known exploited | FixYes | Published05/27/2026 | SeverityHigh |
CVE-2024-5401 | Exploitation statusNot known exploited | FixYes | Published12/04/2025 | SeverityMedium |
CVE-2024-45539 | Exploitation statusNot known exploited | FixYes | Published12/04/2025 | SeverityHigh |
CVE-2024-45538 | Exploitation statusNot known exploited | FixYes | Published12/04/2025 | SeverityCritical |
CVE-2025-1021 | Exploitation statusNot known exploited | FixYes | Published04/23/2025 | SeverityHigh |
CVE-2024-50629 | Exploitation statusNot known exploited | FixYes | Published03/19/2025 | SeverityMedium |
CVE-2024-10445 | Exploitation statusNot known exploited | FixYes | Published03/19/2025 | SeverityMedium |
CVE-2024-10441 | Exploitation statusNot known exploited | FixYes | Published03/19/2025 | SeverityCritical |
CVE-2024-10444 | Exploitation statusNot known exploited | FixYes | Published03/19/2025 | SeverityHigh |
CVE-2024-0854 | Exploitation statusNot known exploited | FixYes | Published01/24/2024 | SeverityMedium |
CVE-2023-2729 | Exploitation statusNot known exploited | FixYes | Published06/13/2023 | SeverityMedium |
CVE-2023-0142 | Exploitation statusNot known exploited | FixYes | Published06/13/2023 | SeverityMedium |
CVE-2022-27622 | Exploitation statusNot known exploited | FixYes | Published10/25/2022 | SeverityMedium |
CVE-2022-27623 | Exploitation statusNot known exploited | FixYes | Published10/25/2022 | SeverityHigh |
CVE-2022-3576 | Exploitation statusNot known exploited | FixYes | Published10/20/2022 | SeverityMedium |
CVE-2022-27624 | Exploitation statusNot known exploited | FixYes | Published10/20/2022 | SeverityCritical |
CVE-2022-27625 | Exploitation statusNot known exploited | FixYes | Published10/20/2022 | SeverityCritical |
CVE-2022-27626 | Exploitation statusNot known exploited | FixYes | Published10/20/2022 | SeverityCritical |
CVE-2022-27616 | Exploitation statusNot confirmed | FixYes | Published08/03/2022 | SeverityHigh |
CVE-2022-22684 | Exploitation statusNot confirmed | FixYes | Published07/28/2022 | SeverityHigh |
CVE-2022-27610 | Exploitation statusNot confirmed | FixYes | Published07/27/2022 | SeverityMedium |
CVE-2022-22687 | Exploitation statusNot confirmed | FixYes | Published03/25/2022 | SeverityCritical |
CVE-2022-22688 | Exploitation statusNot confirmed | FixYes | Published03/25/2022 | SeverityHigh |
CVE-2022-22679 | Exploitation statusNot confirmed | FixYes | Published02/07/2022 | SeverityMedium |
CVE-2021-43929 | Exploitation statusNot confirmed | FixYes | Published02/07/2022 | SeverityMedium |
CVE-2021-43927 | Exploitation statusNot confirmed | FixYes | Published02/07/2022 | SeverityMedium |
CVE-2021-43926 | Exploitation statusNot confirmed | FixYes | Published02/07/2022 | SeverityMedium |
CVE-2021-43925 | Exploitation statusNot confirmed | FixYes | Published02/07/2022 | SeverityMedium |
CVE-2022-22680 | Exploitation statusNot confirmed | FixYes | Published02/07/2022 | SeverityMedium |
CVE-2021-29084 | Exploitation statusNot confirmed | FixYes | Published06/23/2021 | SeverityHigh |
CVE-2021-29085 | Exploitation statusNot confirmed | FixYes | Published06/23/2021 | SeverityHigh |
CVE-2021-29087 | Exploitation statusNot confirmed | FixYes | Published06/23/2021 | SeverityHigh |
CVE-2021-27649 | Exploitation statusNot confirmed | FixYes | Published06/23/2021 | SeverityCritical |
CVE-2021-29086 | Exploitation statusNot confirmed | FixYes | Published06/23/2021 | SeverityMedium |
CVE-2021-26563 | Exploitation statusNot confirmed | FixYes | Published02/26/2021 | SeverityHigh |
CVE-2020-27656 | Exploitation statusNot confirmed | FixYes | Published10/29/2020 | SeverityMedium |
CVE-2020-27652 | Exploitation statusNot confirmed | FixYes | Published10/29/2020 | SeverityHigh |
CVE-2020-27650 | Exploitation statusNot confirmed | FixYes | Published10/29/2020 | SeverityMedium |
CVE-2020-27648 | Exploitation statusNot confirmed | FixYes | Published10/29/2020 | SeverityHigh |
CVE-2018-13293 | Exploitation statusNot confirmed | FixYes | Published04/01/2019 | SeverityMedium |
CVE-2018-13291 | Exploitation statusNot confirmed | FixYes | Published04/01/2019 | SeverityMedium |
CVE-2018-13286 | Exploitation statusNot confirmed | FixYes | Published04/01/2019 | SeverityMedium |
CVE-2018-13284 | Exploitation statusNot confirmed | FixYes | Published04/01/2019 | SeverityHigh |
CVE-2017-16774 | Exploitation statusNot confirmed | FixYes | Published04/01/2019 | SeverityMedium |
CVE-2018-8920 | Exploitation statusNot confirmed | FixYes | Published12/24/2018 | SeverityMedium |
CVE-2018-8917 | Exploitation statusNot confirmed | FixYes | Published12/24/2018 | SeverityMedium |
CVE-2018-8919 | Exploitation statusNot confirmed | FixYes | Published12/24/2018 | SeverityHigh |
CVE-2018-13281 | Exploitation statusNot confirmed | FixYes | Published10/31/2018 | SeverityMedium |
CVE-2018-13280 | Exploitation statusNot confirmed | FixYes | Published07/30/2018 | SeverityHigh |
CVE-2018-8916 | Exploitation statusNot confirmed | FixYes | Published06/08/2018 | SeverityMedium |
CVE-2017-12075 | Exploitation statusNot confirmed | FixYes | Published06/08/2018 | SeverityHigh |
CVE-2017-16766 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2017 | SeverityUnknown |
CVE-2017-15889 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2017 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
