On this page (7 sections)
CISA has added CVE-2024-10441, a critical remote code execution flaw in Synology DiskStation Manager (DSM) and BeeStation OS, to its Known Exploited Vulnerabilities (KEV) catalog. The entry is dated 2026-11-18, which means the bug is being treated as actively exploited. Synology shipped fixes back in 2024, so the practical question today is whether your devices ever received them.
If you run a Synology NAS that hosts website backups, shared files, a staging site or an internal tool, or you manage one for clients, check its DSM version today. A NAS is often reachable from the network in ways the owner has forgotten about, and a compromise there can expose everything stored on it.
What happened
The flaw sits in the system plugin daemon of DSM and BeeStation OS. According to the NVD entry, a remote attacker could execute arbitrary code via unspecified vectors. The CVSS vector shows network access, low complexity, no privileges and no user interaction, which is the profile of a bug that can be attacked automatically at scale.
Synology first published its advisory, Synology-SA-24:20, on 2024-11-05 and labeled it as a Pwn2Own 2024 issue. Technical details were disclosed on 2025-03-19. The matching BeeStation advisory, Synology-SA-24:23, covers the BeeStation side. Synology credits Pumpkin Chang and Orange Tsai of the DEVCORE Research Team, and Ryan Emmons and Team Smoking Barrels, for the set of issues in those advisories.
The new development is the KEV listing. CISA lists a due date of 2026-11-21 for US federal agencies, and its required action is to apply mitigations per vendor instructions or stop using the product if mitigations are unavailable. The research available to us does not say who is exploiting the flaw, how, or how many devices are affected, so treat those details as unconfirmed.
Technical details in plain terms
CWE-116 describes software that builds a structured message for another component but fails to encode or escape data correctly. The result is that attacker-supplied input can change the meaning of the message instead of being treated as plain data. Here, that happens in a background service (the system plugin daemon), and the outcome Synology and NVD describe is arbitrary code execution.
The specific vectors are described only as unspecified, and Synology states that no workaround exists. That matters for your planning: you cannot rely on disabling a single feature, so the only reliable response is to install a fixed release.
The same advisories cover two related, lower severity bugs reported in the same Pwn2Own batch: CVE-2024-50629 (CVSS 5.3, limited file read through the webapi component) and CVE-2024-10445 (CVSS 4.3, improper certificate validation in the update function, requiring an adjacent attacker). Updating to the fixed builds addresses all three.
Exploitation status is the part that changed. As of the GitHub advisory snapshot, the EPSS estimate was 1.251% (70th percentile), but a KEV listing reflects evidence of real-world exploitation and should outweigh that probability score.
Who is affected
Synology's advisories name these products and the builds that contain the fix:
| Product | Upgrade to |
|---|---|
| DSM 7.2.2 | 7.2.2-72806-1 or above |
| DSM 7.2.1 | 7.2.1-69057-6 or above |
| DSM 7.2 | 7.2-64570-4 or above |
| DSM 7.1 | 7.1.1-42962-7 or above |
| DSM 6.2 | 6.2.4-25556-8 or above |
| BeeStation OS 1.0 and 1.1 | 1.1-65374 or above |
| Unified Controller (DSMUC) | 3.1.4-23079 (per the GitHub advisory; Synology's page says DSMUC 3.1 updates were released) |
Devices most at risk are those whose management interface or other services are reachable from the internet, for example through port forwarding, a reverse proxy or a cloud relay. Devices only reachable on a trusted internal network are less exposed but still worth updating, since the bug requires no login.
How to check your exposure
First, find the installed DSM version. In the DSM web interface, open Control Panel, then Info Center, and read the DSM version. You can also read it over SSH on the NAS if you have SSH enabled, with this read-only command, which prints the version file. Compare the build number against the table above.
cat /etc.defaults/VERSIONThen work out whether the device is reachable from outside. From a machine outside your network, check whether your NAS hostname or public IP answers on the DSM ports you use. Also review your router for port-forwarding rules that point at the NAS, and any Synology QuickConnect or DDNS names that are still active.
If you manage a website that stores backups or media on a Synology device, also use the free SSL certificate checker to review certificates on any public hostnames pointing at it, which helps you spot forgotten endpoints.
What to do now
- List every Synology device you own or manage: DSM NAS units, BeeStation devices and any Unified Controller.
- Check each device's version and compare it with the fixed releases in the table above.
- Install the latest available DSM or BeeStation OS update from Control Panel, then Update & Restore (or the vendor download center), and reboot when prompted.
- Remove router port forwards and public exposure for the management interface unless you truly need it. Use a VPN for remote administration instead.
- Turn on automatic security updates for DSM so future fixes arrive without manual work.
- Review admin accounts, scheduled tasks, installed packages and SSH keys for anything you do not recognize, and rotate admin passwords.
- If a device ran an unpatched version while exposed, treat it as possibly compromised and follow your incident process (see the links below).
Because Synology says no mitigation exists, there is no safe middle ground between patching and restricting access. If you cannot update a device right away, limit access to it from the internet as a stopgap and keep it off public networks until the update is installed.
Detection and monitoring after patching
Patching closes the hole but does not tell you whether someone used it earlier. CISA's KEV entry mentions forensics triage requirements for federal stakeholders, which is a useful reminder that exposed, unpatched devices deserve a closer look.
- Check the DSM Log Center and security logs for unexpected logins, new admin users or changes to sharing settings.
- Look for unfamiliar scheduled tasks, startup scripts, packages or processes, and for unexplained outbound connections from the NAS.
- Confirm backups and shared folders are intact, and compare recent file changes against what you expect.
- Keep a short inventory of devices and versions, and recheck it whenever CISA or Synology publish new advisories.
If the NAS hosts or backs up a public website, scanning the site itself is also sensible. An outside-in view will not see inside the NAS, but it can reveal changes to what your site serves. See our guide on what outside-in malware detection can and cannot see and the walkthrough on checking whether a website is hacked. If you do find signs of compromise, follow website hacked: what to do.
Webforta Monitor can watch certificate, DNS and header changes on public hostnames, which is useful for catching unexpected changes to endpoints that point at infrastructure like a NAS.
Timeline
| Date | Event |
|---|---|
| 2024-11-05 | Synology publishes Synology-SA-24:20 (DSM) and Synology-SA-24:23 (BeeStation), labeled Pwn2Own 2024 |
| 2024-11-12 to 2024-12-05 | Fixes for DSM 7.2.1, DSMUC 3.1, DSM 7.1 and DSM 6.2 added to the advisory |
| 2025-03-19 | Vulnerability details disclosed; CVE published to NVD and the GitHub Advisory Database |
| 2026-11-18 | CISA adds CVE-2024-10441 to the KEV catalog |
| 2026-11-21 | CISA due date for federal agencies |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
