
On November 18, CISA added a Synology flaw to its Known Exploited Vulnerabilities catalog, with a fix deadline of Saturday, November 21, for federal agencies. The flaw is CVE-2024-10441, a remote code execution bug in DiskStation Manager, and the patch shipped in November and December 2024. The boxes getting hit now are the ones that never got it.
Nothing about this flaw is new. The advisory is two years old, and the fix has sat on Synology's update servers since before most of these NAS boxes were last rebooted. What changed this week is that CISA now has evidence the flaw is being used in real attacks, and Synology confirmed on October 29 that ransomware operators are encrypting outdated DSM devices.
What CISA confirmed, and what nobody has confirmed
CISA's entry says CVE-2024-10441 is an improper encoding or escaping of output flaw in the system plugin daemon of DSM and BeeStation OS, and a remote attacker can use it to run arbitrary code. The entry was added November 18, 2026, the federal remediation date is November 21, and CISA marks it as requiring forensic triage, so agencies must also check whether affected systems were already compromised. CISA lists known ransomware campaign use as Unknown. It names no attacker and no campaign.
That gap matters, because a ransomware campaign is in the news and it is tempting to join the two together. Synology's October 29 statement says threat actors are exploiting "a vulnerability patched in December 2024" against devices running outdated DSM, and that the attacks aim to encrypt data and extort ransom. It names no CVE, and when BleepingComputer asked which flaw was being used, a Synology spokesperson pointed to the same 2024 advisory. The ransomware in the victim reports is called C3RB3R. It leaves a ransom note named read-me3.txt, renames files with a .L0CK3D extension, and points victims at a dark-web portal to buy a "C3rb3r Decryptor."
But the C3RB3R entry point is not settled. Qihoo 360 linked C3RB3R attacks to two different DSM flaws, CVE-2026-13684 and CVE-2026-13639, fixed by Synology in September 2026 under advisory SA-26:13. Neither CISA nor Synology has said CVE-2024-10441 is the flaw C3RB3R uses. The honest version: CISA has evidence CVE-2024-10441 is being exploited, and Synology has confirmed ransomware is hitting outdated DSM boxes. Whether those are the same attacks is unconfirmed.
That uncertainty does not change what you should do. Do not wait for someone to name the exact flaw before you patch. The patch closes a 9.8 remote code execution hole either way, and waiting for attribution while an unauthenticated RCE sits on your network is not a plan.
The flaw, in one paragraph
CVE-2024-10441 sits in DSM's system plugin daemon. Synology rates it Critical with a CVSS 3.1 score of 9.8, and the vector needs no login, no user interaction, and only network access: AV:N/AC:L/PR:N/UI:N. A remote attacker can execute arbitrary code on the box. It was one of three flaws from the Pwn2Own 2024 contest, published in advisory Synology-SA-24:20 on November 5, 2024. The other two are a limited file read and a limited file write, both moderate. The advisory lists no workaround. Its Mitigation field reads "None." The only fix is the update.
Find out where your boxes stand
The check takes two minutes per box. Open DSM, go to Control Panel, then Info Center, and read the full build string. "DSM 7.2" tells you nothing. You need the whole thing, for example 7.2.1-69057-6.
| DSM branch | Minimum fixed build |
|---|---|
| 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 boxes need BSM 1.1-65374 or above. Do not forget the BeeStation in the corner, the old unit at a branch office, or the one a supplier runs that holds your backups. Shadowserver counts more than 380,000 Synology NAS devices reachable from the internet, and the exposed ones are what this campaign is built for.
The four moves
1. Update to a current release, not just the 2024 minimum. Meeting the table above closes CVE-2024-10441. It does not close everything else. On November 10, Synology published advisory SA-26:19 for CVE-2026-76954, a 9.8 SQL injection in the DSM Auth API that needs no login, plus an rsync authentication bypass rated 8.6. The fixed builds are 7.4.1-90080-1, 7.3.2-86009-5, 7.2.2-72806-10, and 7.2.1-69057-13, and proof-of-concept code for the SQL injection is already public. No exploitation has been reported for it yet, and it is not in CISA's catalog. That is the time to patch it, before it is. In Control Panel, go to Update and Restore, then DSM Update, and install the latest build for your model. As of this week the current releases are DSM 7.4.1 and DSM 7.3.2. If a box cannot run a supported DSM release, plan to replace it. Patching a dead branch is borrowed time.
2. Turn on automatic updates. This is Synology's own recommendation, and it is the fix for the actual failure here: nobody in this story was breached by a zero-day. They were breached by a patch they never installed. In DSM Update settings, turn on automatic installation of important updates. A NAS is the one box in the house that should never need you to remember it.
3. Take DSM management off the internet. DSM's management page listens on ports 5000 and 5001 by default. If your router forwards those ports, or QuickConnect exposes the login page, anyone on the internet can reach the service these flaws live in. Remove the port forwards, turn off QuickConnect if you do not need it, and put admin access behind a VPN or an allow list.
4. Check the backup the NAS cannot reach. Updating closes the hole. It does not decrypt files that are already locked. And a backup that lives on the same NAS, or on a share the NAS can write to, is not a recovery plan. It is a second copy in the same blast radius. Confirm that at least one copy of your data sits somewhere the NAS cannot touch: an offline drive, a cloud bucket, or an immutable backup target. Then test a restore, because a backup you have never restored from is a hope, not a plan.
The durable point
Synology rarely issues a warning like the October 29 statement. BleepingComputer notes the last comparable alert was in August 2019, during the brute-force campaign that delivered eCh0raix ransomware. A vendor that almost never says it is being attacked just said it, about a flaw fixed two years ago.
That is the part worth remembering after the deadline passes. The NAS in the closet is infrastructure, not an appliance. It holds the photos, the documents, and very often the only backup, and it needs the same treatment as any server: a patching cadence, a build number you can state from memory, and a backup you have tested. The 2024 patch was the easy part. The hard part was noticing that the box had gone two years without it.
Sources
- CISA, Known Exploited Vulnerabilities Catalog (CVE-2024-10441 added November 18, 2026; catalog version 2026.11.18)
- Synology, "Synology urges users to update DSM following ransomware attacks on outdated DSM versions" (October 29, 2026)
- Synology, Synology-SA-24:20 DSM (PWN2OWN 2024) (November 5, 2024; last updated March 28, 2025)
- Synology, Synology-SA-26:19 DSM (November 10, 2026)
- BleepingComputer, "Synology warns of C3RB3R ransomware attacks targeting NAS devices" (November 2, 2026; updated November 3, 2026)
- NVD, CVE-2024-10441 (published March 19, 2025)



