Synology DSM RCE flaw exploited in the wild (CVE-2024-10441)
At a glance
| Severity | CRITICAL |
|---|---|
| CVSS | CVE-2024-10441: 9.8 |
| EPSS (30-day exploit probability) | CVE-2024-10441: 1.3% |
| In CISA KEV (exploited) | Yes, due 2026-11-21 |
| Vendor | Synology |
| CVE IDs | CVE-2024-10441 |
Primary-source details
- CVE-2024-10441: CVSS 9.8 (Critical), per NVD; fixed in synology diskstation manager: 7.2-64570-4, 7.2.1-69057-6, 7.2.2-72806-1 (NVD); added to the CISA KEV catalog on 2026-11-18, remediation due 2026-11-21; vendor advisory (listed by NVD).
CISA added a Synology DiskStation Manager (DSM) remote code execution flaw, CVE-2024-10441, to its Known Exploited Vulnerabilities catalog on 2026-11-18, which means it is exploited in the wild. Federal agencies must apply the vendor mitigations by 2026-11-21, and every other DSM owner should treat that date as their own deadline.
The NVD scores the bug 9.8 (critical). The Synology DSM vulnerability sits in the system plugin daemon and lets a remote attacker run arbitrary code, according to the NVD record.
What happened
CISA’s catalog entry describes the issue as an improper encoding or escaping of output flaw in the system plugin daemon of Synology DSM and Synology BeeStation OS (BSM). A remote attacker can use it to execute arbitrary code through unspecified vectors. The catalog does not say who is exploiting it or how, and CISA lists known ransomware campaign use as “Unknown”.
The weakness is tracked as CWE-116. The NVD entry was first published on 2025-03-19, so the fix has been available for a long time. We are covering it now because CISA confirmed active exploitation on 2026-11-18, which changes this from a routine patch to an urgent one.
That gap matters. Any device that missed the original update has been exposed to a critical, network-reachable flaw for months, and administrators who closed the ticket long ago may not realise the risk has changed.
Am I affected?
The NVD lists these products as affected:
- Synology DiskStation Manager 7.2 builds before 7.2-64570-4
- Synology DiskStation Manager 7.2.1 builds before 7.2.1-69057-6
- Synology DiskStation Manager 7.2.2 builds before 7.2.2-72806-1
- Synology BeeStation OS 1.0, 1.0.1, 1.0.2 and 1.1 (fixed in a release before 1.1-65374 according to the NVD description)
Synology’s advisories for this CVE are Synology_SA_24_20 and Synology_SA_24_23, both referenced by the NVD.
Technical details
- Attack vector: network, no privileges and no user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base score 9.8).
- Exploitation status: listed in CISA KEV, added 2026-11-18, due date 2026-11-21.
- EPSS: 1.25%, the model’s estimate of exploitation probability. KEV listing shows exploitation is happening regardless of that low score.
- Exact exploit method: not published; the NVD says “unspecified vectors”.
Why this matters
Analysis, not new facts. Appliances like NAS units are often left outside normal patch cycles because they are seen as storage rather than servers, and they rarely run endpoint security tooling that would flag an intruder.
NAS devices hold backups, shared files and credentials, and many are reachable from the internet for remote access. A pre-authentication code execution bug on such a device gives an attacker a strong foothold and a place to stage data theft or ransomware.
Because the flaw is in KEV, patch within hours rather than the next maintenance window. Devices exposed to the internet come first, then internal units.
What to do
- Inventory every DSM and BeeStation OS device, including forgotten ones at branch offices and in home labs.
- Update DSM to at least 7.2-64570-4, 7.2.1-69057-6 or 7.2.2-72806-1, depending on your branch. Check Synology’s advisories for the BeeStation OS fixed release.
- If you cannot patch immediately, remove the device from direct internet exposure, restrict management access to a VPN or an allow-list, and disable services you do not use.
- CISA’s required action points to its BOD 26-04 guidance and its forensics triage requirements. Follow them if you run federal systems, and treat them as good practice elsewhere.
- Hunt for compromise on unpatched devices: unexpected admin accounts, new scheduled tasks or packages, unknown outbound connections, and changes to shared folders or backups. No indicators of compromise have been published.
Record the firmware build of every device after updating so you can prove which units were exposed and when they were fixed. Tell your incident response team if an exposed device was running a vulnerable build, because patching does not remove an attacker who is already inside.
Related coverage
Sources
- CISA Known Exploited Vulnerabilities catalog: CVE-2024-10441
- NVD: CVE-2024-10441
- Synology advisory SA-24-20
- Synology advisory SA-24-23
- FIRST EPSS
