Your Backup Is the Target: Synology NAS RCE (CVE-2024-10441) Now Exploited by Ransomware
A critical unauthenticated RCE in Synology's DiskStation Manager, patched back in 2024, is being exploited now against internet-exposed NAS devices by a ransomware crew, and it has landed in CISA's exploited-vulnerabilities catalog. The device holding your backups is the one getting encrypted. Here's the fix.
Executive summary. CVE-2024-10441 is a critical (CVSS 9.8) unauthenticated remote code execution flaw in Synology DiskStation Manager (DSM) and BeeStation OS, in the system plugin daemon. Synology patched it in 2024 (Synology-SA-24:20), but it is now being actively exploited against internet-exposed, outdated NAS devices by the C3RB3R ransomware operation, and recent reporting says CISA added it to the Known Exploited Vulnerabilities catalog (KEV status was contested across sources, so verify directly). The attack is brutally simple: scan the internet for old Synology NAS, exploit without credentials, and encrypt the data the organisation was relying on for recovery. Two related flaws (CVE-2024-50629 file read, CVE-2024-10445 file write) were reported in the same campaign. The fix has existed for over a year, patch, and get the NAS off the public internet.
What it is
| Field | Detail |
|---|---|
| CVE | CVE-2024-10441 (+ CVE-2024-50629, CVE-2024-10445 in-campaign) |
| Product | Synology DSM and BeeStation OS (system plugin daemon) |
| Type | Unauthenticated RCE |
| Severity | 9.8 Critical |
| Status | Exploited by C3RB3R ransomware; reported CISA KEV (verify) |
| Fixed | DSM 7.2.2-72806-1 / 7.2.1-69057-6 / 7.2-64570-4 / 7.1.1-42962-7 / 6.2.4-25556-8; BSM 1.1-65374 (Synology-SA-24:20, 2024) |
Why NAS ransomware hurts more
A NAS is where organisations and prosumers keep file shares and backups. When the NAS itself is the entry point:
- The attacker reaches the data directly — and often the backups meant to save you.
- Many NAS are internet-exposed for remote access (QuickConnect, port-forwarding), putting the device on the front line.
- They're frequently unmanaged and unpatched — bought, set up, and forgotten, exactly the long-tail of exposure attackers scan for.
Encrypting the backup target turns a recoverable incident into a crisis. That's why edge storage appliances are a favourite ransomware target.
The attack, start to finish
- Attacker scans the internet for Synology NAS running outdated DSM/BSM.
- Exploits CVE-2024-10441 for unauthenticated code execution on the device.
- Runs as the device's privileged service; may chain the file read/write flaws.
- C3RB3R ransomware encrypts the stored data — including backups kept on the same NAS.
Note: some sources say the exact attack path isn't fully confirmed, so treat the specific CVE-to-ransomware link as reported, not settled; the remediation is the same either way.
Remediation
Now
- Update DSM/BeeStation OS to the fixed builds (Synology-SA-24:20) — check the exact build string in DSM Update, don't compare only the leading "7.2". Apply the fixes for the related CVEs too.
- Remove internet exposure. Disable port-forwarding to the NAS and unnecessary QuickConnect; put remote access behind a VPN. A NAS should not be directly reachable from the internet.
Resilience
- 3-2-1 backups: at least one copy offline/immutable and off the NAS, so an encrypted NAS isn't the end of your recovery.
- Least privilege and MFA on NAS accounts; disable default/admin accounts; restrict admin to the LAN.
Detection and hunting
| Where | Look for |
|---|---|
| Synology logs | Unexpected connections to the NAS from the internet; new/modified packages or services; new admin users |
| Files | Mass file modification/encryption; ransom notes; unusual deletions of snapshots/backups |
| Network | The NAS making outbound connections to unfamiliar hosts |
| Exposure | Confirm whether your NAS is reachable from the internet (Shodan-style self-check) |
Conclusion
CVE-2024-10441 is a reminder that "patched in 2024" means nothing if the device was never updated — and that internet-exposed NAS are prime ransomware targets precisely because they hold the data and the backups. The fix is a year old; the exposure is the real problem.
Do this now: update DSM/BSM to the fixed builds, take the NAS off the public internet (VPN only), and make sure at least one backup copy is offline/immutable and not on the NAS.
Related: our network pentesting manual chapter on service enumeration.
Sources: SecurityOnline (KEV batch), Rescana (C3RB3R), Penligent, Exploit-Intel. KEV status and the exact attack path were contested across sources; confirm against CISA's catalog and Synology-SA-24:20.
Related research
Administrator Without a Password: The VMware vCenter Auth Bypass a Chinese APT Rode for Months
A flaw in vCenter's identity layer lets anyone with network access become Administrator without a password, and Google's Mandiant says a China-nexus group quietly exploited it as a zero-day since September to deploy backdoors. Broadcom's emergency patch is out. Here's the chain, who's exposed, and how to hunt.
Chrome's Eighth Zero-Day of 2026: CVE-2026-125350, a Use-After-Free in XML
A single malicious web page can corrupt memory in Chrome's XML engine and run code inside the sandbox, and Google says it's already being exploited. It's the eighth Chrome zero-day of the year. Here's the bug, the fix, why an un-relaunched browser stays vulnerable, and how to roll it out across a fleet.
CVE-2026-76466: A Pre-Auth Root RCE in Cisco Expressway, Exploited Hours After the PoC
A trust assumption between clustered Cisco Expressway nodes lets an unauthenticated attacker reach the cluster database and run code as root on the collaboration edge, and attackers moved within hours of a public proof of concept. Here's the chain, who's exposed, and what to do today.