All articles

NewsNovember 18, 20264 min read

Synology DSM and BeeStation: CVE-2024-10441 exploited (CISA KEV)

CISA confirms exploitation of CVE-2024-10441, an unauthenticated RCE (CVSS 9.8) in Synology DSM and BeeStation OS: fixed versions and what to do now.

Laptop whose screen has been turned into the armoured door of a safe

On 18 November 2026 the US CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities (KEV) catalog. It is an improper encoding or escaping of output vulnerability in Synology DiskStation Manager (DSM), the operating system of Synology NAS devices. According to the description in the National Vulnerability Database (NVD), the same flaw also affects Synology BeeStation OS (BSM). Inclusion in the catalog means CISA has evidence of real-world exploitation.

This article is based on a single source: the CISA entry in the KEV catalog, with data from the NVD. The entry does not say who is exploiting the flaw, against which organisations, since when or with which tools.

What the KEV entry says

  • Name: Synology DiskStation Manager (DSM) Improper Encoding or Escaping of Output Vulnerability.
  • Added to the catalog: 18 November 2026.
  • Deadline for US federal agencies: 21 November 2026, just three days after inclusion.
  • Known use in ransomware campaigns: unknown («Unknown»).
  • Required action: apply mitigations according to the vendor’s instructions, in line with CISA’s BOD 26-04 directive on prioritising security updates based on risk and its «Forensics Triage Requirements»; for cloud services follow the same directive, or stop using the product if mitigations are not available. CISA also asks organisations to assess the internet exposure of every asset.

The reference to forensic triage requirements means that updating is not enough: you also need to check whether the device has already been compromised.

Technical details

According to the NVD description, the flaw lies in the system plugin daemon and allows remote attackers to execute arbitrary code. The description refers to «unspecified vectors»: the service or request used for exploitation is not public.

  • Weakness: CWE-116, improper encoding or escaping of output.
  • CVSS 3.1: 9.8 (critical), assigned by Synology, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H: network attack, low complexity, no privileges and no user interaction required, high impact on confidentiality, integrity and availability.
  • NVD record status: published on 19 March 2025, last modified on 18 November 2026 («Modified»).

Among its references, the NVD lists two vendor advisories: Synology-SA-24:20 and Synology-SA-24:23.

In MITRE ATT&CK terms, remote exploitation of a network-reachable service corresponds to T1190 (Exploit Public-Facing Application). The entry does not include any public indicators of compromise.

Affected versions

According to the NVD description and CPE configurations:

Product Affected versions Fixed version
DSM 7.2 from 7.2 before 7.2-64570-4 7.2-64570-4
DSM 7.2.1 from 7.2.1-69057 before 7.2.1-69057-6 7.2.1-69057-6
DSM 7.2.2 from 7.2.2 before 7.2.2-72806-1 7.2.2-72806-1
BeeStation OS (BSM) 1.0, 1.0.1, 1.0.2 and 1.1 1.1-65374

Compare the version down to the build and update number (the part after the hyphen): a DSM 7.2.2 device is not safe just because it is on that branch. For DSM branches not listed, the entry gives no information: check their status in Synology’s advisories.

What it means for European organisations

In many companies, especially SMEs, the NAS is the shared file server and often also the backup target for other systems. Unauthenticated remote code execution on this device puts both working data and the ability to restore at risk. The KEV catalog is binding only on US federal agencies, but it is widely used as a reference when prioritising updates. For organisations subject to NIS2 (in Italy, Legislative Decree 138/2024), which must manage vulnerabilities based on risk, a critical flaw with confirmed exploitation should be handled with top priority; the same applies to healthcare organisations that store documents or patient data on a NAS.

What to do now

  1. Inventory: identify all Synology NAS devices running DSM and all BeeStation devices, including those in branch offices or managed by suppliers, and compare their version with the table.
  2. Update: install the fixed versions given in advisories Synology-SA-24:20 and Synology-SA-24:23, and check in the device’s control panel that they have been applied.
  3. Exposure: as CISA asks, assess whether the management interface or other device services can be reached from the internet or from untrusted networks. If they are not needed, close them; for remote access, prefer a VPN.
  4. Hunt for compromise, as CISA requires with forensic triage: review device logs, existing accounts and installed packages, looking for activity or changes that do not match known operations.
  5. Backups: make sure you have copies of important data outside the NAS, on disconnected or immutable media.
  6. If you cannot update immediately, follow the vendor’s mitigations or, as CISA indicates, consider not using the device until they are available. Updating does not remove access an attacker has already gained: if you see suspicious signs, treat the event as an incident.

How ARXDOME helps

ARX Expose shows what can be seen of your company from outside, including exposed services and known vulnerabilities on public services: a NAS management panel reachable from the internet shows up there. ARX Scout verifies, with your authorisation, which perimeter ports are really open and, with ARX Scout Assessment, flags outdated software and exposed administration panels. ARX Radar, using firewall logs, shows who is attacking your perimeter right now.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles