Skip to content
Breach Index · running record

Synology vulnerabilities in 2026: DSM CVE-2024-10441 and ransomware on outdated NAS devices (not a breach of Synology)

Synology makes the DiskStation network-attached storage (NAS) devices that many small offices, labs and departments use for file shares and backups. This page tracks exploited vulnerabilities in Synology's DSM operating system and separates what Synology says from what researchers report.

Short answer

Was Synology hacked?

No, CVE-2024-10441 is not a breach of Synology: nothing reported shows an intrusion at Synology. It is a vulnerability in DiskStation Manager (DSM), fixed in November 2024 (Synology-SA-24:20), that lets a remote attacker execute code without logging in (CVSS 3.1 9.8).

On 29 October 2026 Synology warned that attackers were exploiting a vulnerability it patched in December 2024 to encrypt data on devices running outdated DSM and demand a ransom, and pointed customers to Synology-SA-24:20. CISA added CVE-2024-10441 to its Known Exploited Vulnerabilities catalog on 18 November 2026, due 21 November. The risk is to owners of devices that were never updated.

Timeline at a glance

  1. 5 Nov 2024Synology-SA-24:20 fixes CVE-2024-10441 (DSM 7.2.2-72806-1 and equivalents; BeeStation OS 1.1-65374). (Synology)Not a breach
  2. 18 Sep 2026Synology-SA-26:13 fixes two more CVSS 9.8 DSM flaws (CVE-2026-13684, CVE-2026-13639). (Synology)Not a breach
  3. 29 Oct 2026Synology warns of ransomware attacks on outdated DSM and urges updates; it names no CVE. (Synology)Confirmed
  4. 18 Nov 2026CISA adds CVE-2024-10441 to KEV, due 21 November 2026; ransomware use "Unknown". (CISA)Not a breach

Last updated 20 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

Synology incident timeline, in detail

Confirmed = acknowledged by Synology, a regulator filing or a court. Reported = credible reporting Synology has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Oct-Nov 2026Not a breachProduct vulnerability (pre-authentication), known exploited

CVE-2024-10441: pre-authentication code execution in DSM, exploited against outdated devices

What happened. Improper encoding or escaping of output in the DSM system plugin daemon (CWE-116) lets remote attackers execute arbitrary code. Fixed in DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 and 7.1.1-42962-7, and BeeStation OS 1.1-65374. Found at Pwn2Own 2024; the CVE record credits Ryan Emmons.

Impact. Synology says attackers exploited a flaw it patched in December 2024 to encrypt data on outdated DSM devices and extort a ransom. CISA lists CVE-2024-10441 as exploited (forensic triage "Yes", ransomware use "Unknown"). The Hacker News reports the ransomware as C3RB3R, citing Qihoo 360 and customer reports.

Sources: Synology-SA-24:20 · Synology notice · CVE record · CISA KEV · The Hacker News

Where the reports disagree

  • Which flaw: Synology's 29 October notice names no CVE and says the flaw was patched in December 2024, while the advisory it links (SA-24:20) was published in November 2024. CISA ties the exploitation to CVE-2024-10441. Qihoo 360, as reported by The Hacker News, links the C3RB3R ransomware to two newer flaws in Synology-SA-26:13.
  • Ransomware name: C3RB3R appears in the URL of Synology's notice and in The Hacker News's report, but not in the text of Synology's notice.

The pattern across the record

Old patches, new attacks

The fix was 23 months old when CISA listed it. NAS devices are often bought by a department, never registered with IT and never updated.

Vulnerabilities are not breaches

Nothing here is an intrusion at Synology. The exposure is to owners of devices that missed the update.

What it means for Synology customers — and what to do

If you own Synology NAS devices, the question is which DSM build each one runs and whether its management interface faces the internet, not whether Synology was breached.

  1. 1.Update DSM

    Move every device to the current build of its branch, which covers both SA-24:20 and SA-26:13, and turn on automatic updates.

    Fixed versions
  2. 2.Take DSM off the internet

    Use a VPN for remote management rather than exposing DSM ports.

  3. 3.Protect the backups

    Keep an offline or immutable copy so ransomware on the NAS is not the end of the data.

    3-2-1-1-0 checker
  4. 4.Check KEV and set the deadline

    Federal due date 21 November 2026.

    KEV checker
Take this with you
Incident timeline · What Synology customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 20 November 2026.

  1. 1.Synology-SA-24:20 DSM (Pwn2Own 2024) — Synology, 5 Nov 2024
  2. 2.Synology-SA-26:13 DSM — Synology, 18 Sep 2026
  3. 3.Synology urges users to update DSM following ransomware attacks — Synology, 29 Oct 2026
  4. 4.CVE-2024-10441 — CVE.org, 19 Nov 2026
  5. 5.CISA Adds Four Known Exploited Vulnerabilities to Catalog — CISA, 18 Nov 2026
  6. 6.Synology NAS devices targeted (C3RB3R) — The Hacker News, 3 Nov 2026

Frequently asked questions

Was Synology hacked?

No breach of Synology is reported. CVE-2024-10441 is a vulnerability in its DSM software, fixed in November 2024 and exploited against devices that were never updated.

Which DSM version fixes CVE-2024-10441?

DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 or 7.1.1-42962-7 or later. Synology-SA-26:13 needs newer builds again, so update to the current build of your branch.

Is CVE-2024-10441 used by ransomware?

Synology says attackers exploited a DSM flaw it patched in December 2024 to encrypt data and demand ransom, and points to SA-24:20. CISA marks ransomware use "Unknown". The Hacker News names the ransomware C3RB3R.

Our coverage of Synology

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by Synology. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.