Synology says attackers are targeting outdated DiskStation Manager (DSM) installations to encrypt files and demand ransom. Its October 29 notice says the attacks exploit a vulnerability patched in December 2024. It urges owners to update and enable automatic updates.

Evidence status: attacks reported by the affected vendor. Synology links to an advisory covering several flaws but does not name the specific CVE in its notice or give a victim count.

Update — November 18, 2026, 17:50 EST

CISA now independently lists CVE-2024-10441 as exploited in the wild. Its November 18 catalog entry names the system plugin daemon in DSM and BeeStation OS. This is a new exploitation-status assessment of an older flaw, not a new vulnerability disclosure.

The vendor advisory identifies these historical repair boundaries for CVE-2024-10441: BeeStation OS 1.1-65374, DSM 7.2-64570-4, DSM 7.2.1-69057-6 and DSM 7.2.2-72806-1. Use the latest supported model-specific update, since these minimums address only this older defect.

CISA’s listing supplies no campaign attribution or victim count. Its ransomware-use field remains Unknown, so the entry does not prove that CVE-2024-10441 caused every C3RB3R case described below.

The catalog flags forensic triage and lists November 21 as its due date under the federal BOD 26-04 framework. That is a federal compliance context, not a blanket deadline for home NAS owners. For an exposed, unpatched device, coordinate evidence preservation and containment with the update; CISA’s guidance explains why patching can erase useful artifacts.

Check the right update for your device

The linked 2024 advisory includes CVE-2024-10441, a remotely exploitable code-execution flaw, alongside other vulnerabilities. Its listed fixed releases vary by DSM branch. Those historical minimums do not cover every later flaw.

Separate reporting by IT-Connect describes security firm 360’s investigation of C3RB3R ransomware and its attribution to two different DSM flaws. Synology’s September 2026 advisory identifies these as CVE-2026-13639 and CVE-2026-13684. It lists fixes at DSM 7.4-90075, 7.3.2-86009-4, 7.2.2-72806-9, and 7.2.1-69057-12, or later on those branches.

These accounts do not establish the entry route for every incident. Check the latest supported DSM and package updates for the exact NAS model, rather than stopping at an old advisory’s minimum. If a device can no longer receive fixes, consider replacing it or isolating it from untrusted networks.

Protect access and prepare recovery

  • Remove unnecessary direct internet exposure of the management interface. Use a trusted VPN for remote administration and restrict access to necessary users.
  • Enable multifactor authentication, review accounts and unused services, and keep separate offline or otherwise protected backups. Test a restore.
  • If encryption is underway, isolate the device from the network and seek incident-response help. Preserve the ransom note and logs; coordinate containment and evidence collection before rebooting or upgrading.

A software update closes known vulnerabilities; it does not decrypt files or establish that an already affected system is clean. IPSIP’s incident review discusses the limits of reported recovery methods and notes that volatile evidence can be lost on reboot.

Caveat: Synology and 360 sell security-related products or services. Their reports do not establish the scale of the campaign or a universal recovery method.