Security advisory · Synology
Remote code execution in Synology DSM and BeeStation OS
CVE-2024-10441 lets a remote attacker run code on Synology DSM and BeeStation OS devices without authentication. Synology rates it critical, and CISA added it to the Known Exploited Vulnerabilities catalog in November 2026. The fix is to update to the patched build for your line.
What is affected and how serious it is
The flaw is in the system plugin daemon. Synology, as the issuing CNA, describes it as an “improper encoding or escaping of output” issue (CWE-116) that “allows remote attackers to execute arbitrary code via unspecified vectors”. It is reachable over the network without authentication. Synology rates it CVSS 3.1 9.8 (critical) with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. We use “critical” because the vendor does; the number is Synology’s own.
Affected products and fixed versions
Fixed builds come from the CVE record. Update to the patched build for your product line.
| Product line | Fixed in |
|---|---|
| DSM 7.2.2 | 7.2.2-72806-1 |
| DSM 7.2.1 | 7.2.1-69057-6 |
| DSM 7.2 | 7.2-64570-4 |
| DSM 7.1 | 7.1.1-42962-7 |
| BeeStation OS (BSM) 1.0 and 1.1 | 1.1-65374 |
What is known about exploitation
CISA added CVE-2024-10441 to the Known Exploited Vulnerabilities (KEV) catalog on 18 November 2026, on evidence of active exploitation. The catalog entry records ransomware use as “Unknown”, which means CISA has not tied it to a named ransomware campaign, not that it is ruled out. We found no public, primary-source detail on how the devices are being attacked, and we do not infer beyond what CISA states. For internet-exposed devices that ran unpatched, CISA asks organizations to perform a forensic triage.
How to check your exposure from outside
Run these checks only on devices you own or are authorized to test. They are passive reads of what the device already serves.
-
Spot the DSM interface
The DSM web interface is usually served on ports 5000 and 5001, or behind a reverse proxy. Its login page and
/webman/paths identify it. -
Look for a build number
Static resources under
/webman/sometimes carry a build identifier in a query string. If the exact build is not visible from outside, the finding is tentative: you can see the product but not prove the version. -
Keep it passive
A plain request to the login page and its static resources is enough to recognize the device. There is no need to send anything that touches the vulnerable code.
-
Confirm from the admin panel
The reliable check is inside the device: Control Panel, then Update & Restore, shows the installed version so you can compare it with the fixed build.
How to fix it
- Update DSM or BeeStation OS to the fixed build for your line, from Control Panel, then Update & Restore.
- Reduce exposure. If the device does not need to be reachable from the internet, turn off remote access such as QuickConnect and port forwarding, or place it behind a VPN.
- Check for compromise. If the device was exposed while unpatched, look for signs of intrusion; CISA requests a forensic triage for affected, internet-facing devices.
How NorthBound looks at this
Appliances like a network-attached storage device often sit on the edge of a network with their management interface exposed. As part of tech stack intelligence, we recognize such interfaces and match them to new CVEs, enriched with CISA KEV context. When the exact build is not visible from outside, we flag the device as tentative rather than confirmed, and the check stays passive. Our team reviews each match and tells your engineers what to prioritize. We do not attempt exploitation.
Sources
Find it before an attacker does.
Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.
Facts on this page verified 11 November 2026.