Our Thinking / Field Notes / The Security Watch

EVOLVING SECURITY ADVISORY / SYNOLOGY DISKSTATION MANAGER (DSM) SECURITY: CVE-2024-10441 ADDED TO CISA KNOWN EXPLOITED VULNERABILITIES

Synology DSM Exploited Vulnerability: Is Your NAS at Risk?

CISA added Synology DSM flaw CVE-2024-10441 to its exploited-vulnerabilities list on 18 November 2026. Here are the fixed builds, how to check your NAS, what to do now and what to look for if an old, exposed device has been reachable.

What matters now

Current position: Patch available; exploitation of CVE-2024-10441 listed by CISA KEV on 18 November 2026

Affected versions: DSM before 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7 and 6.2.4-25556-8 for their respective branches; BeeStation OS 1.0 and 1.1 before 1.1-65374.

Observed exploitation: CISA lists CVE-2024-10441 as exploited in the wild. Synology separately reports ransomware attacks on outdated DSM but has not named the CVE used. CISA lists known ransomware campaign use as Unknown.

Recommended next action: Update DSM to at least the fixed build for your branch (preferably the latest available), remove internet exposure of the management interface, and check devices that were outdated and reachable for signs of compromise.

Identifiers: CVE-2024-10441

Immediate guidance

If your Synology NAS runs a DSM build older than the fixed build for its branch (7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7 or 6.2.4-25556-8), update it now and make sure its management interface is not reachable from the internet. CISA added CVE-2024-10441, a critical remote code execution flaw in DSM, to its Known Exploited Vulnerabilities catalogue on 18 November 2026. If an outdated NAS has been internet-facing, patching is not enough on its own: check it for signs of compromise as well.

What we know as of 19 November 2026

On 18 November 2026 CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities (KEV) catalogue, its list of flaws with credible evidence of real-world exploitation. The entry is titled as an improper encoding or escaping of output vulnerability in Synology DiskStation Manager (DSM). Synology rates it Critical, with a CVSS score of 9.8: it can be reached over the network, needs no login and needs no user interaction. The flaw is in the system plugin daemon and lets a remote attacker run code on the NAS. The public description gives no detail about the attack route.

Synology fixed it in advisory Synology-SA-24:20, first published on 5 November 2024, with fixes arriving branch by branch over the following weeks. The advisory lists no workaround. The fix is the update.

Separately, Synology said on 29 October 2026 that attackers were exploiting a vulnerability patched in December 2024 against devices running outdated DSM, with the aim of encrypting data and demanding a ransom. It pointed to the same advisory but did not name a CVE. Press reports have linked that campaign to the C3RB3R ransomware. So the position is this: exploitation of CVE-2024-10441 is confirmed by CISA, and Synology has confirmed ransomware attacks on outdated DSM, but Synology has not publicly said that this particular CVE is the entry point for those attacks. CISA's own entry marks known ransomware use as Unknown. Treat the connection as likely but not confirmed.

Being on the KEV list tells you the flaw is being used. It does not tell you who has been hit, and we are not aware of any organisation publicly and credibly linked to this CVE.

Which Synology devices are affected

The flaw affects DSM builds older than the fixed build for each branch below. Anything at or above the listed build has the fix for this CVE. Synology's table does not list DSM 7.3 or 7.4 as affected by it.

Synology rates DSM 6.2 as Moderate rather than Critical for this advisory, but the fixed build still matters if you are running that branch.

  • DSM 7.2.2: fixed in 7.2.2-72806-1
  • DSM 7.2.1: fixed in 7.2.1-69057-6
  • DSM 7.2: fixed in 7.2-64570-4
  • DSM 7.1: fixed in 7.1.1-42962-7
  • DSM 6.2: fixed in 6.2.4-25556-8
  • BeeStation OS (BSM) 1.0 and 1.1: fixed in 1.1-65374, under the related advisory Synology-SA-24:23

Check your version and exposure

Two questions decide how urgent this is: how old is your DSM build, and could anyone on the internet reach the NAS login page? You need to be signed in to DSM as an administrator for the first check, and you need access to your router or firewall for the second.

  1. In DSM, open Control Panel, then Info Center, and read the DSM version on the General tab. Compare the full build number, including the part after the final dash, against the list above. A device on 7.2.2-72806 with no further suffix is behind 7.2.2-72806-1.
  2. Look for ways in from outside. In your router or firewall, check for port forwarding rules, DMZ or UPnP mappings pointing at the NAS. DSM's web interface uses ports 5000 and 5001 by default, though yours may have been changed. In DSM, also check whether QuickConnect or an external DDNS address is switched on.
  3. Treat the result as a decision. Current build and no internet exposure: you are in good shape, so carry on to the update advice below. Old build and no exposure: update promptly, since the flaw is still reachable by anything on your internal network. Old build and exposed at any point: update and also work through the compromise checks further down.

Update DSM and close the internet-facing door

Updating DSM restarts the NAS, so file shares, backups, sync jobs and any hosted apps will be unavailable while it installs. Pick a quiet moment, let running backups or large copies finish first and warn anyone who depends on the device. Synology's updates are cumulative within a branch, so you do not need to install older fixes first. Only the DSM administrator account can run the update.

If your NAS may be compromised, do not run through this list first. Go to the compromise checks, because updating and rebooting can destroy evidence and a freshly patched device can still hold an attacker's access.

  1. Take the NAS off the internet before you do anything else if it is exposed: remove the router port forwards or DMZ entry for it and turn off QuickConnect if you do not need it. Management interfaces on a NAS rarely need to be public, and a VPN into your network is the safer way in if you need remote access.
  2. In DSM, open Control Panel, then Update & Restore, and check for a DSM update. Install the newest update offered for your branch rather than stopping at the minimum build listed above. Newer DSM releases have since fixed other critical flaws, covered in the next section. The device will restart, and it may take several minutes to come back. Carry on once you can sign in again.
  3. Return to Info Center and confirm the DSM version now meets or exceeds the fixed build for your branch.
  4. In the same Update & Restore area, check the update settings and turn on automatic DSM updates if the device is not managed in some other way. Synology itself recommends automatic updates.
  5. If DSM offers no update for your hardware or branch, for example an older model stuck on a branch below the fixed build, do not leave it exposed. Keep it off the internet, restrict who on your network can reach it, and plan its replacement or a move to a supported branch.

If an outdated NAS was reachable from the internet

Exploitation of this flaw lets an attacker run code, so installing the patch closes the hole without removing anything that came through it. CISA's entry for this vulnerability also flags forensic triage under its Binding Operational Directive 26-04, which is its way of saying that US federal agencies must check for prior compromise, not just patch. The directive binds only those agencies, but the logic applies to anyone.

The visible sign in the reported ransomware attacks is files renamed with a .L0CK3D extension and a ransom note called read-me3.txt. Those details come from press reporting, not from Synology, and an attacker with access need not be that obvious. Quiet access, such as new accounts or scheduled tasks, would not show up that way.

If you see encrypted files or a ransom note, disconnect the NAS from every network straight away, pause sync and backup jobs that touch it so encrypted data does not spread, and avoid restoring anything onto the affected device. Keep the ransom note and a few encrypted samples. Check whether you hold clean, offline or separately stored backups before wiping anything. If the device holds personal data, speak to whoever handles your data protection obligations promptly, because reporting duties can apply.

If everything looks normal but the device was old and reachable, check DSM's user list for accounts you do not recognise, review Task Scheduler for jobs you did not create, look at recent sign-in activity in the logs, and change administrator and service passwords from a separate trusted computer after patching. If you cannot rule out access and the NAS holds important data, get a specialist to assess it before it goes back into service.

Newer DSM advisories to know about

CVE-2024-10441 is a two-year-old flaw, and the latest Synology advisories show why sitting on an old build is a poor bet. These newer issues are separate from the CISA entry, and none of the Synology advisories below states that it is being exploited.

Synology-SA-26:19, last updated 13 November 2026, fixes a critical SQL injection in the Auth API (CVE-2026-76954) and a high-severity authentication bypass in rsync (CVE-2026-85101). Fixed builds include 7.2.2-72806-10, 7.3.2-86009-5 and 7.4.1-90080-1.

Synology-SA-26:21, published on 19 November 2026 and still marked Ongoing, covers a critical flaw in the OAuth API (CVE-2026-120382) affecting DSM 7.1 to 7.4 and BeeStation OS 1.5. At the time of checking, Synology lists fixed builds for DSM 7.3 and 7.4 as scheduled by 20 November 2026, recommends moving 7.2.1 and 7.2.2 to 7.3.2-86009-6 or later, and gives no fix date for DSM 7.1 or BeeStation OS. Its one listed mitigation is to deactivate the OAuth Service package. Check what, if anything, relies on that package before you stop it, and re-read the advisory for current fix status before acting.

Update history

We’ll keep this page updated as new information becomes available. Check back for the latest developments.

  1. Initial notice, 19 November 2026: CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities catalogue on 18 November 2026, with a federal due date of 21 November 2026. Synology's advisory Synology-SA-24:20 lists the fixed builds and no workaround. Synology's 29 October 2026 ransomware warning does not name the CVE used. Update source

Technical terms explained
CVSS
The Common Vulnerability Scoring System, a 0 to 10 score for technical severity. It does not measure how likely an attack is.
Known Exploited Vulnerabilities
A list maintained by the US cyber agency CISA of vulnerabilities for which it has credible evidence of exploitation in real attacks. Being listed does not identify who was attacked.
port forwarding
A router rule that sends traffic arriving from the internet on a chosen port to a device inside your network, such as a NAS.
QuickConnect
Synology's relay service that lets you reach a NAS from the internet without opening router ports. It still puts the NAS login within reach of the internet.
remote code execution
A flaw that lets an attacker run their own commands on a device from elsewhere on a network, without physical access.

Sources and further reading

KEEP THE CONVERSATION GOING

Not sure whether your NAS was exposed?

If you would like a second pair of eyes on a Synology device, its exposure or a possible compromise, we can help you work out where you stand.

Contact Rismor