Why End-of-Life NAS Firmware Is a Ransomware Liability
Security Intermediate 5 min read

Why End-of-Life NAS Firmware Is a Ransomware Liability

End-of-life NAS firmware keeps serving data after fixes stop. Why attackers target it, what the Synology C3RB3R campaign shows, and how to plan replacement.

Published: November 19, 2026 • Updated: November 19, 2026
end-of-lifenasfirmwareransomwarelifecycle

End-of-life NAS firmware is a ransomware liability because the device keeps running, keeps holding your data and keeps accepting connections long after the vendor stops fixing it. The C3RB3R campaign against Synology devices in late 2026 exploited CVE-2024-10441, a bug patched two years earlier, and Hong Kong's CERT said the attacks targeted end-of-life DiskStation Manager versions specifically. This piece explains why a NAS on an unsupported firmware branch belongs on a replacement schedule, not a watch list.

What does end-of-life mean for a NAS?

End-of-life for a NAS means the vendor has stopped publishing security fixes for that hardware model or that firmware branch. The device still boots, serves files and runs backups, but any vulnerability found after the cutoff stays open permanently. For an appliance that listens on the network and stores the organization's data, that is a different risk category from an old laptop.

Synology states that its NAS products receive firmware and software updates for up to five years. After that window, or when a DSM branch is retired, the fixed builds in new advisories simply do not list the old branch. The September 2026 advisory Synology-SA-26:13, which fixed two CVSS 9.8 bugs, lists builds for DSM 7.4, 7.3, 7.2.2 and 7.2.1 only. If your device is on 7.2, 7.1 or 6.2, there is no fix to install for those bugs.

Why do attackers prefer old NAS firmware?

Old firmware gives attackers a published vulnerability, a public write-up and a large population of devices that will never be patched. Each of those lowers the cost of a campaign. Exploit development is already done, scanning for the version string is cheap, and the targets do not change from week to week.

The Synology case is the template. The vendor published SA-24:20 in November 2024 and fixed CVE-2024-10441 across every branch by December 5, 2024. Technical details were disclosed in March 2025. Victims started appearing in mid-October 2026. BleepingComputer reports more than 380,000 Synology devices visible on the internet per Shadowserver. The attackers did not need a zero-day. They needed patience and a scanner. The full timeline is in our report on Synology DSM CVE-2024-10441 and C3RB3R ransomware.

The same C3RB3R operators previously went after Confluence and GitLab servers using vulnerabilities from 2021 and 2023, again long after patches existed. Backup servers are a favored variant of the pattern: the AhsayCBS zero-days used to mine cryptocurrency on backup servers hit the same class of always-on, rarely updated infrastructure.

Why a NAS compromise is worse than a workstation compromise

Three properties make a NAS a high-consequence target:

  • It is the data. A workstation holds one person's working files. A NAS holds the department's, often the company's.
  • It is frequently the backup target. Synology's own ransomware guidance describes the NAS as the destination for workstation, server and virtual machine backups. If the device that stores backups is encrypted, the backups go with it unless a copy exists somewhere the NAS cannot reach.
  • It runs as an appliance. Nobody logs in daily, so there is no one to notice a slow update prompt or an unfamiliar process. HKCERT's advice for suspected infection, which includes pausing sync and backup jobs so the encryption does not replicate, exists because by the time anyone notices, the damage has spread.

A NAS that is also end-of-life compounds all three. You cannot patch it, you probably rely on it, and you are unlikely to be watching it.

The partial-fix trap

Vendors sometimes extend one fix to a retired branch under pressure. Synology did this in 2026 for PHP2Shell, shipping PHP package updates for DSM branches back to 6.2. HKCERT's note on that decision is the important part: those fixes do not mean that end-of-life DSM versions have returned to full support. A single backported patch is a courtesy, not a commitment. Planning around it leaves every other post-cutoff bug open.

The same logic applies to compensating controls. Taking the management interface off the internet, enforcing MFA and keeping immutable backups all reduce exposure, and the steps are in how to secure a Synology NAS against ransomware. None of them fix a pre-authentication code execution bug in a daemon that still listens on the LAN. An attacker who lands on any workstation on that network has a path to the NAS that no amount of perimeter work closes.

How do you decide when to replace a NAS?

Replace it when the vendor stops listing its firmware branch in critical advisories, when it cannot run the current supported DSM release, or when its model has passed the vendor's stated support window, whichever comes first. HKCERT's guidance on the 2026 attacks is direct: upgrade to the latest DSM version supported by both the device and the vendor, and if the device cannot run a supported version, consider replacing it.

CISA's KEV catalog uses similar language in its required action for CVE-2024-10441: apply mitigations per vendor instructions, or discontinue use of the product if mitigations are unavailable. For federal agencies that is a directive. For everyone else it is a reasonable policy statement to adopt as written.

Building the replacement schedule

Treat NAS devices the way a mature shop treats phones and firewalls, with a dated retirement plan. We made the same argument for handsets in why unsupported iPhones belong on a retirement schedule; the storage version has higher stakes. A practical schedule has four parts:

  1. Inventory every NAS, including the ones in branch offices, home offices and under desks. Record model, DSM branch, full build string, whether it is reachable from the internet, and what it stores.
  2. Record each device's support end date from the vendor's product status page and the date its current DSM branch last appeared in a critical advisory.
  3. Set a replacement trigger at twelve months before the support end date, so budget and migration happen before the window closes rather than after an incident.
  4. Move the data before the deadline. Replication to a supported device is straightforward while both sides are healthy. It is not straightforward after one side has been encrypted.

Budget owners sometimes object that the hardware still works. It does. So did every Synology that was encrypted in October 2026. The question is not whether the device functions but whether anyone will fix the next critical bug in it. For end-of-life firmware the answer is already known.