FR
live

The C3RB3R ransomware is encrypting Synology NAS still running DSM outdated since December 2024

On October 29, 2026, Synology confirmed that attackers are exploiting a vulnerability patched in December 2024 to encrypt data on NAS boxes running outdated DSM, via the C3RB3R ransomware. Update DSM now, take the admin interface off the internet, and move your backups off the NAS.

A row of hard-drive caddies in a dim server rack, one caddy pulled slightly forward with an amber padlock hanging from its handle.

October 29, 2026. Synology confirms that threat actors are exploiting a vulnerability patched in December 2024 to target NAS boxes running outdated DSM. November 5, 2024. The Synology-SA-24:20 advisory, born out of Pwn2Own 2024, published the fix — three CVEs, including an unauthenticated code execution rated 9.8. November 2, 2026. BleepingComputer reports a wave of encryption by the C3RB3R ransomware, which appends the .L0CK3D extension to files. Why it matters: boxes left unpatched for nearly two years are being encrypted right now, and the vendor itself is asking for an immediate update.

For anyone self-hosting a Synology at home or in a small business, this is not one more alert. It is proof that the patch gap on a NAS — the device that holds the files and, too often, the only backup — has become a profitable attack line.

A vulnerability patched nearly two years ago, exploited today

The whole affair is a story of an ignored fix. The Synology-SA-24:20 advisory, titled “DSM (PWN2OWN 2024),” was published on November 5, 2024 and last updated on March 28, 2025. Its overall severity is Critical, its status Resolved, and its mitigation field reads “None”: the update is the only defense.

The advisory covers three flaws. The most serious is CVE-2024-10441, rated 9.8 in CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H): an unauthenticated remote code execution flaw in the system plugin daemon, described as an “improper encoding or escaping of output.” It affects DSM before 7.2-64570-4, 7.2.1-69057-6, and 7.2.2-72806-1, as well as BeeStation OS (BSM) before 1.1-65374. Two Moderate flaws round out the set: CVE-2024-50629 (limited file read via the webapi component, 5.3) and CVE-2024-10445 (limited write via the update function’s certificate validation, 4.3).

The patch timeline says it all. DSM 7.2.2 was fixed on November 5, 2024, 7.2.1 on November 12, 7.1 on November 26, and 6.2 on December 5, 2024. Any box still exposed today has missed fixes that have been available for almost two years.

C3RB3R: an opportunistic ransomware following a familiar pattern

The ransomware, named C3RB3R — also known as Cerber and CerberImposter — drops a read-me3.txt ransom note and appends the .L0CK3D extension to encrypted files. Its name is borrowed from a notorious ransomware-as-a-service operation that emerged in 2016; since December 2021 it has already been used against Confluence and GitLab servers, riding on public RCE and authentication-bypass flaws.

The pattern is therefore classic: a commodity ransomware, deployed against exposed devices that missed a public patch. No group has claimed this campaign, and attribution remains open.

The most telling signal is the history. Synology rarely warns customers about active attacks: the last comparable alert was the 2019 brute-force campaign that delivered eCh0raix ransomware, and the vendor also warned about StealthWorker in 2021. That it breaks silence in 2026 to say “update now” measures the gravity of the moment.

What Synology is not saying — and why it changes the playbook

One point is deliberately vague. Synology says a vulnerability “patched in December 2024” is being exploited, but does not say which of the three CVEs in SA-24:20 is at fault. Asked by BleepingComputer, a spokesperson simply pointed back at the 2024 advisory.

CVE-2024-10441 is the obvious candidate: it is the only one of the three offering unauthenticated remote code execution, exactly the vector a campaign against internet-reachable NAS boxes would use. But it is not a confirmed exploited CVE — it does not appear in the CISA KEV catalog as of November 3, 2026, and neither do the other two.

That ambiguity has a clear operational consequence: do not ask “which CVE?” — patch everything. The advisory spans several DSM branches — 7.2.2, 7.2.1, 7.2, 7.1, and 6.2 — and the US release also names the PHP2Shell flaws (Synology-SA-26:14) as a separate issue to patch in parallel if PHP packages (Web Station, WordPress, MailStation, Calendar) are installed.

The last trap is semantic. The global statement says “outdated” DSM; the US release says “end-of-life” DSM. Either way, the target is a version below the fixed builds, and a box that cannot run a supported DSM release should be replaced, not merely patched.

What to do right now

The remediation comes down to four moves, in order.

  • Update DSM immediately. Bring every box to the fixed build of its branch — 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7, or 6.2.4-25556-8 — and turn on automatic updates as the vendor recommends.
  • Take management off the internet. Remove port forwards to the DSM admin interface (5000/5001 by default) and put admin access behind a VPN or an allow-list.
  • Move backups off the NAS. A backup stored on the same box, or on a share it can write to, is not a recovery plan. Use offline or immutable backups and test the restore.
  • Patch PHP2Shell separately. If PHP packages are active, apply the Synology-SA-26:14 fixes too — the vendor has not linked PHP2Shell to the ransomware, but it is parallel hygiene, not a substitute for the DSM update.

If files are already encrypted, the sequence changes: isolate the box from the network, pause sync and backup jobs, preserve the ransom note and logs, then restore from a clean backup — after cleaning and patching. Installing the update does not decrypt what is already encrypted.

Verdict

C3RB3R is not a sophisticated campaign: it is a commodity ransomware harvesting NAS boxes still on DSM that has been out of date for nearly two years. The fix exists, it is public, and the vendor says it plainly — the update is the only defense.

If you host a Synology below the fixed builds, update today: the flaw has no mitigation, and encryption is already underway on exposed fleets. If your box listens on the internet, pull the management interface off public ports — that is the move that turns a target into an invisible asset. And if your NAS is your only backup, accept that you have no backup: an offline, immutable copy is the only thing that turns a ransomware into a mere inconvenience. The lesson of C3RB3R is not technical — it is that self-hosting does not forgive a patch gap, especially when the device stores everything.

References

The cyber brief, every Tuesday

The flaws that matter and the patches to apply, in a ten-minute read.

No spam. One-click unsubscribe.
read next

On the same topic

selfh.st’s 2026 survey puts numbers on the Portainer exodus: 66% to 33% in a year

selfh.st’s annual survey, published November 12, 2026 from 6,221 responses (+52%), shows Portainer falling from 66% to 33% share among container-management tool users, overtaken by the Dockhand, Komodo, and Arcane wave, while 60% of respondents already use AI. If your homelab runs on Portainer CE, this shift is about you.

Immich 3.4.0 brings tags to the mobile apps, two years after their web launch

On November 10, 2026 Immich shipped version 3.4.0, finally bringing tags — launched in August 2024 but confined to the web — to the mobile apps, alongside JPEG XL and passkeys. If you organized your library with tags, mobile parity is here; upgrade and set MACHINE_LEARNING_MODEL_REVISION=v2 to reclaim the ML container’s memory win.

← Back to the feed

Type at least two characters.

↑ ↓ navigate ↵ open esc dismiss