CISA flags active exploitation of Synology DSM flaw CVE-2024-10441
On 18 November 2026, CISA added CVE-2024-10441, a remote code execution flaw in Synology DiskStation Manager, to its Known Exploited Vulnerabilities catalogue. Organisations running Synology NAS devices on DSM or BeeStation OS should apply the vendor's guidance promptly.
What to do now
- Product
- Synology DiskStation Manager (DSM) / BeeStation OS (BSM)
- Affected versions
- Not stated in the source; see Synology advisory Synology_SA_24_20
- Fixed in
- Not stated in the source
- CVE
- CVE-2024-10441
The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2024-10441 to its Known Exploited Vulnerabilities catalogue on 18 November 2026. A KEV listing means the flaw is being exploited in real attacks. It affects Synology DiskStation Manager (DSM), the operating system that runs Synology's network-attached storage devices.
The bug is an improper encoding or escaping of output weakness, classified as CWE-116. CISA places it in the system plugin daemon and names Synology BeeStation OS (BSM) in its description. A remote attacker could use it to run arbitrary code. The exact attack vectors have not been disclosed.
The source does not say which versions are vulnerable or which versions contain the fix. It points to Synology's security advisory Synology_SA_24_20, and administrators should use that advisory to confirm affected DSM and BSM releases and the update to install.
Under Binding Operational Directive 26-04, US federal agencies have until 21 November 2026 to act. CISA has also marked this flaw as requiring forensic triage, which suggests that exposed devices may already have been compromised before patching. Where no mitigation is available, CISA advises discontinuing use of the product. It is not currently known whether the flaw has been used in ransomware campaigns.
What to do now
- Inventory every Synology NAS running DSM or BeeStation OS, starting with any device reachable from the internet.
- Read Synology advisory Synology_SA_24_20 and apply the update or mitigations it specifies.
- Until a fix is in place, remove direct internet exposure from these devices and restrict access to trusted networks, as general good practice.
- Check logs and system state on exposed devices for signs of compromise, such as unfamiliar processes, accounts or scheduled tasks.