CISA Lists a 2024 Synology NAS Flaw as Exploited, Three Weeks After Synology Warned of Ransomware
CISA says CVE-2024-10441 in Synology DiskStation Manager is exploited, three weeks after Synology warned of ransomware on outdated DSM. The fixed versions, what is and is not confirmed, and a six-step check for a small office NAS.

In this article
Table of Contents
Table of contents
CISA added CVE-2024-10441, a critical remote code execution flaw in Synology DiskStation Manager (DSM), to its Known Exploited Vulnerabilities catalogue on Wednesday 18 November, with a due date of Saturday 21 November for US federal agencies. The listing arrives three weeks after Synology warned that attackers were using a vulnerability it fixed in December 2024 to encrypt data on NAS devices still running outdated DSM. Neither Synology nor CISA says the two are the same flaw, and that gap matters for what you do next. The fix for CVE-2024-10441 has existed since 2024.
#What CISA’s entry says, and what it leaves out
CISA’s catalogue entry names the flaw as an improper encoding or escaping of output vulnerability in the system plugin daemon, and says a remote attacker could use it to run arbitrary code through unspecified vectors. The entry gives the weakness class as CWE-116, sets the federal due date at 21 November and marks “known ransomware campaign use” as Unknown. It also carries a “forensic triage” flag set to Yes, and its required action refers to CISA’s forensic triage requirements, which we read as an expectation that agencies look for signs of compromise as well as patching.
What the entry does not say is who is exploiting the flaw, how many devices are affected, or how the attacks work. Synology’s own advisory rates the bug Critical, with a CVSS 3.1 score of 9.8 and a vector that needs no login and no user interaction: network reachable, low complexity. The advisory lists the mitigation as “None”. In practice that means the only vendor-approved answer is the update.
The National Vulnerability Database record was published on 19 March 2025 and was modified again on the morning of 19 November, after the catalogue listing. It points back to the Synology advisory and to CISA’s catalogue.
#Two warnings three weeks apart
On 29 October, Synology put out a short statement saying it had “identified threat actors exploiting a vulnerability patched in December 2024 to target devices running outdated versions of DSM”, and that “these attacks aim to encrypt data and extort ransom”. It urged anyone on a vulnerable version to update immediately, recommended turning on automatic updates, and pointed readers to the same advisory, Synology-SA-24:20. It did not name a CVE.
The Hacker News reported on 3 November that customers had said their devices were hit by C3RB3R ransomware, which renames encrypted files with a .L0CK3D extension and leaves a ransom note called read-me3.txt. It also said the Chinese security vendor Qihoo 360 had published an analysis describing C3RB3R as having a long history against NAS devices, including through two DSM flaws that Synology fixed in September 2026, CVE-2026-13684 and CVE-2026-13639. Security Affairs, the same day, made the point we would make: the advisory covers three flaws, and Synology had not confirmed which one attackers were using, so none of the three should be treated as a confirmed entry point.
Put the dates side by side and the record is untidy:
| Date | What happened | Source |
|---|---|---|
| Tuesday 5 November 2024 | Synology publishes advisory SA-24:20 for DSM, covering CVE-2024-10441, CVE-2024-50629 and CVE-2024-10445 | Synology advisory |
| Thursday 5 December 2024 | Fixed release for DSM 6.2 added, the last branch to get one | Synology advisory revision history |
| Wednesday 19 March 2025 | CVE-2024-10441 record published | NVD |
| Thursday 29 October 2026 | Synology warns of ransomware attacks on outdated DSM | Synology statement |
| Tuesday 3 November 2026 | Press reports name C3RB3R, and cite a vendor analysis pointing at two other DSM flaws | The Hacker News, Security Affairs |
| Wednesday 18 November 2026 | CISA lists CVE-2024-10441 as exploited | CISA catalogue |
| Saturday 21 November 2026 | CISA’s due date for federal agencies | CISA catalogue |
Synology says the exploited flaw was patched in December 2024; the reports on C3RB3R mention September 2026 fixes; CISA lists a flaw whose fixes shipped between November and early December 2024. We cannot reconcile those from public information, and we will not pretend to. What we can say is that all three point the same way: a NAS that has not taken updates is the target.
#Which Synology devices need attention
Synology’s advisory lists the fixed releases, and the first thing to do is compare the full version string on your device, not only the major number.
| DSM branch | Severity in the advisory | Upgrade to at least |
|---|---|---|
| 7.2.2 | Critical | 7.2.2-72806-1 |
| 7.2.1 | Critical | 7.2.1-69057-6 |
| 7.2 | Critical | 7.2-64570-4 |
| 7.1 | Critical | 7.1.1-42962-7 |
| 6.2 | Moderate | 6.2.4-25556-8 |
The CVE record also names Synology BeeStation OS before 1.1-65374 as affected. The advisory rates the 6.2 branch Moderate and the others Critical; we would still update a 6.2 device, because the update closes a flaw rated Critical on the other branches.
#Why an old NAS bug matters to a small office
In our reading, a NAS is often the one box in a small office that holds the shared drive, the accounts folder and the backupsThe KBY LexiconBackupA causally disconnected, point-in-time copy of system state, tagged with a consistency marker, that lets you recover from logical corruption or data loss independent of the source system's health. , and it is easy to set up once and never open again. Security Affairs makes the same point: businesses often keep shared documents, operational files and backup copies on one system, so ransomware on it reaches well beyond the device.
That is our reading of why this listing is worth a story even though the bug is two years old. A flaw that needs no login only becomes a business problem if the device can be reached, so the question for a small firm is not “is it on the list” but “can anyone on the internet reach it”. Remote access features, port forwards on the router and dynamic DNS names are common ways a NAS ends up reachable, and they are easy to set up and forget.
If your firm is covered by, or working towards, Cyber Essentials, this is the requirement in action: our Cyber Essentials guide sets out that updates the vendor rates critical or high risk must be installed within 14 days of release. A NAS still missing a critical update from 2024 would fail that on its own.
#Check your NAS in this order
- Find the version. In DSM 7, open Control Panel, then Info Center, and read the full DSM version (menu names differ slightly on 6.2). Compare it with the table above.
- Find out whether it is reachable. Ask whoever manages the router or firewall whether any port forwarding or remote-access feature points at the NAS. If you cannot get an answer, assume it is reachable.
- Update. Install the fixed release for your branch through Control Panel, then Update & Restore. Synology recommends enabling automatic updates; turn them on if they are off.
- Until it is updated, take it off the internet. Synology lists no mitigation, so this is our advice rather than the vendor’s: remove the port forward or disable remote access until the update has gone on.
- Look for signs of trouble. Files ending in
.L0CK3Dor aread-me3.txtnote, as reported for C3RB3R, mean you should stop and disconnect the device from the network. - Check you can restore. Confirm that you hold a backup that is not stored on the same NAS or reachable from it, and that a restore actually works. Our backup lexicon entry explains the terms.
#If you think you were hit
Do not pay or negotiate before you have taken advice. Disconnect the NAS from the network, keep it powered and untouched if you can, and speak to your IT provider. If personal data was encrypted or taken, ask your IT provider or a data protection adviser straight away whether it counts as a personal data breach you must report to the ICO, because the reporting deadline runs from when you become aware. Report the attack to Action Fraud as well.
#Our view: treat this as live, but do not oversell the link
We think this is a patch-this-week item for anyone with a Synology on the network, and a drop-everything item for anyone whose NAS is internet-facing. The reasoning is plain. CISA’s catalogue is for flaws it has evidence are being exploited. The flaw needs no login. Synology has separately said ransomware crews are hitting devices that missed a December 2024 fix, and CVE-2024-10441 is the only flaw in that advisory scored Critical. None of that proves that CVE-2024-10441 is the flaw in the C3RB3R attacks, and we are not claiming it. If the public record changes, for example if Synology names the CVE, we will update this story.
What would prove us wrong: Synology or a researcher showing that the ransomware attacks rely on a different flaw and that CVE-2024-10441 is exploited only by someone else. The advice would not change much, because the update closes a critical hole either way. The harder judgement is about the devices that cannot be updated. A box stuck on an old branch with no fix is a device to retire from the network, not one to leave on a port forward, and that decision should be made now rather than after the data is gone.
This is also a pattern. We wrote earlier on Thursday about a LiteLLM flaw added to the same list, and our morning briefing noted this entry. The common thread is old fixes meeting unpatched systems. The US due date is not a UK obligation, but the 14-day rule in Cyber Essentials was missed long ago on any device still running a build from 2024.
#Questions to put to whoever looks after your NAS
- “What DSM version are we on, and is it at or above the fixed release for our branch?”
- “Can the NAS be reached from the internet, by any route, and who approved that?”
- “Are automatic updates on, and who is told if one fails?”
- “Where is the backup that does not live on this device, and when did we last test a restore?”
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01CISA Known Exploited Vulnerabilities cataloguecisa.gov
- 02Synology security advisory Synology-SA-24:20synology.com
- 03Synology press release, 29 October 2026synology.com
- 04The Hacker News, 3 November 2026thehackernews.com
- 05Security Affairs, 3 November 2026securityaffairs.com
- 06NVD record for CVE-2024-10441services.nvd.nist.gov
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Read-only scripts
- Windows devices with no BitLocker recovery key in Entra IDMicrosoft Entra ID, Windows
- Intune devices that haven't synced in N daysMicrosoft Intune
- Mailboxes forwarding to external addressesExchange Online
- BitLocker status of every volume on this PCWindows
Upcoming deadlines
- Intune moves to macOS 15 and laterQ4 2026
- SAP SuccessFactors provisioning: move from basic auth to workload identityNovember 2026
- Intune November release: JIT registration reminder at APNs renewal and automatic JIT for eligible tenantsNovember 2026
Explore KBY
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
SubscribeMore news
All newsWas this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.




Comments
Add a thoughtful note on CISA Lists a 2024 Synology NAS Flaw as Exploited, Three Weeks After Synology Warned of Ransomware. Comments are checked for spam and held for moderation before appearing.