CVE-2024-10441 was published in NVD on March 19, 2025. CISA added it to the KEV catalog on November 18, 2026, with a deadline of November 21 — three days.
Twenty months between disclosure and confirmed exploitation is a long gap. The flaw's profile explains why it resurfaces: unauthenticated remote code execution on a NAS, a box that holds data and that plenty of people expose to the Internet so they can reach it from outside.
Last week we covered another DSM flaw: the SQL injection in the Auth API (CVE-2026-76954).
The Vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2024-10441 |
| CVSS 3.1 (Synology, CNA) | 9.8 (CRITICAL) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD score | none of its own |
| Type | Improper encoding or escaping of output (CWE-116) |
| Component | system plugin daemon |
| Authentication | none |
| NVD publication | 2025-03-19 |
| NVD status | Modified |
| Added to CISA KEV | 2026-11-18 |
| CISA deadline | 2026-11-21 |
NVD description (excerpt):
Improper encoding or escaping of output vulnerability in the system plugin daemon in Synology BeeStation OS (BSM) […] and Synology DiskStation Manager (DSM) […] allows remote attackers to execute arbitrary code via unspecified vectors.
What we know, and what we don't
The description is deliberately thin: "via unspecified vectors". Neither NVD nor the KEV entry describes the mechanism or the exploitation campaign. What is established:
- the bug sits in a system daemon, not in an optional Package Center app;
- the CVSS vector Synology published is the worst case: network, no privileges, no user interaction;
- CWE-116 covers output that is improperly encoded or escaped, a class of defect that often leads to injection — that's a reading of the CWE, not a detail the vendor has published.
The KEV entry says "DSM" in its title, but the description also names BeeStation OS, the system running BeeStation devices. Both are affected.
Affected Versions
| Product | Affected range (NVD) | First version outside the range |
|---|---|---|
| DSM 7.2 | 7.2 up to, but excluding, 7.2-64570-4 | 7.2-64570-4 |
| DSM 7.2.1 | 7.2.1-69057 up to, but excluding, 7.2.1-69057-6 | 7.2.1-69057-6 |
| DSM 7.2.2 | 7.2.2 up to, but excluding, 7.2.2-72806-1 | 7.2.2-72806-1 |
| BeeStation OS | 1.0, 1.0.1, 1.0.2, 1.1 (through build 65373) | 1.1-65374 |
⚠️ These are range boundaries from NVD, not necessarily the version to install today: DSM has shipped many updates since March 2025. Install the latest release for your branch, and check the details in advisories Synology-SA-24:20 and Synology-SA-24:23, both cited in the references.
NVD only lists the DSM 7.2.x branches. If you still run something older, check the Synology advisories to see whether it is in scope.
To check your version: Control Panel → Info Center → General.
Why Three Days
The three-day deadline is deliberate. CISA uses it for flaws it treats as priorities, and the entry points to directive BOD 26-04 and its forensic triage requirements: patching isn't enough, you also need to check whether the device was compromised beforehand.
A NAS that hasn't been updated since 2024 and is reachable from the Internet should be handled as potentially compromised, not just vulnerable.
Detection
- DSM or BSM version below the boundaries above: that's the first cut
- Exposure: is the DSM web interface (ports 5000/5001 by default) or QuickConnect reachable from the Internet?
- Logs (Log Center): unusual sign-ins and system events, especially during the window the device was vulnerable
- Scheduled tasks and boot scripts you didn't create
- Unknown accounts, or disabled accounts that were re-enabled
- Outbound traffic initiated by the NAS to unfamiliar destinations
Mitigation
1. Update
Install the latest DSM or BeeStation OS release for your branch. CISA deadline: November 21.
2. Remove direct exposure
A NAS admin interface has no business being reachable from the Internet. Put it behind a VPN and restrict access to trusted addresses with the DSM built-in firewall.
3. If the NAS was exposed and out of date
- Assume the update does not remove anything an attacker may have dropped
- Rotate the NAS account passwords and the secrets stored on it (backup credentials, sync keys)
- Make sure your backups have an offline or immutable copy the NAS can't modify
Why Continuously Monitor Your Synology Fleet
A flaw published in March 2025 and forgotten since can become urgent overnight, with three days to act. The only way to respond in time is to know, at any moment, which version every NAS is running.
With cveo.tech, inventory your Synology devices with their exact versions and get an alert as soon as a CVE affecting them lands in the CISA KEV catalog, even when it's months old.