Synology DSM vs QNAP QTS: Which Is More Secure in 2026?

CISA just added Synology DSM's first-ever Known Exploited Vulnerability. Here's how DSM's 2026 security record stacks up against QNAP QTS.

Synology DS925+ NAS device, the DiskStation hardware that runs Synology DSM
The Synology DS925+ NAS, which runs the DSM operating system covered in this comparison. Image: Synology.

Synology DSM and QNAP QTS have had very different 2026s. Synology's DSM just picked up its first-ever listing on CISA's Known Exploited Vulnerabilities (KEV) catalog — CVE-2024-10441, a critical remote-code-execution bug CISA confirmed is being actively exploited, with a patch deadline of November 21, 2026 — while also absorbing its most severe advisory wave of the year, Synology-SA-26:19, just days earlier. QNAP's QTS, by contrast, has no 2026 KEV entries at all, but carries a longer historical tail of 12 KEV-listed flaws from 2022–2023, the era of the DeadBolt and Qlocker ransomware waves. Neither platform is "unhackable," and neither vendor's 2026 patch record is spotless — but the data points to QNAP having quietly cleaned up its KEV exposure since 2023, while Synology is now facing the kind of active-exploitation scrutiny QNAP spent years working through.

What just happened: Synology's first KEV listing

On November 18, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2024-10441 to its Known Exploited Vulnerabilities catalog. The flaw is an improper-encoding vulnerability in the system plugin daemon used by DSM and BeeStation OS (BSM), originally disclosed in 2024 and carrying a CVSS 3.1 base score of 9.8 (critical) per Synology's own advisory, Synology-SA-24:20. The NVD's record for the flaw is available at nvd.nist.gov. CISA's KEV due date is November 21, 2026, binding on U.S. federal civilian agencies but widely treated as an urgency signal for everyone else. Fixed builds have been available since 2024 (DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7, and 6.2.4-25556-8, or later), so the KEV listing isn't about a missing patch — it's about CISA confirming the two-year-old bug is now being used in real attacks against unpatched boxes. We covered the KEV addition itself in a separate report the day it happened; this piece looks at what it says about Synology's and QNAP's broader security postures heading into 2026, and how the two platforms' advisory histories actually compare.

Track records compared: KEV history, 2022–2026

CISA's KEV catalog is a useful, if blunt, proxy for "which vulnerabilities actually got exploited," since an entry only appears once there's confirmed evidence of in-the-wild attacks. Pulling the current catalog gives a lopsided picture at first glance:

VendorTotal KEV entriesDate range2026 entries
Synology120261 (CVE-2024-10441)
QNAP122022–20230

Read naively, QNAP looks far worse — twelve confirmed-exploited flaws versus Synology's one. But the dates matter: every QNAP KEV entry dates to 2022 or 2023, clustered around the Photo Station, File Station and NAS command-injection bugs that ransomware crews such as DeadBolt and Qlocker weaponized against internet-exposed devices. QNAP's own QSA-22-19 advisory confirms DeadBolt "appears to target QNAP NAS devices running outdated versions of QTS 4.2.x, 4.3.x and 4.4.x" and outdated bundled apps — versions that are now three to four major releases behind. Nothing QNAP has shipped in QTS 5.2.x has reached KEV status in the three years since. Synology's single entry, meanwhile, is brand new as of this week. Twelve old entries and zero new ones is a different risk profile than one entry that just appeared — but it's also only one data point in each direction, and KEV status says nothing about the dozens of other CVEs each vendor patches every year that never get exploited at scale.

Synology DSM's 2026 security record

Synology's November 2026 patch cycle has been unusually heavy. In addition to the now-KEV-listed CVE-2024-10441, Synology shipped Synology-SA-26:19 on November 13 — rated Critical — covering CVE-2026-76954, a SQL-injection flaw in the DSM Auth API scored 9.8, and CVE-2026-85101, an rsync authentication-bypass bug scored 8.6. That followed Synology-SA-26:18 (Important, November 10) and Synology-SA-26:14, nicknamed "PHP2Shell" (Critical, October 31). Fixed builds for the SA-26:19 flaws are DSM 7.4.1-90080-1, 7.3.2-86009-5, and 7.2.2-72806-10 or 7.2.1-69057-13, depending on branch. None of this month's new critical CVEs are (yet) KEV-listed; only the two-year-old CVE-2024-10441 is. Synology runs a standing Security Bug Bounty Program through its Product Security Incident Response Team (PSIRT, established 2016), paying up to $30,000 for operating-system vulnerabilities, and has separately sponsored Pwn2Own contests that have produced DSM findings in past years.

QNAP QTS's 2026 security record

QNAP's 2026 has been busier in raw CVE count but, per its own advisories, lower in confirmed severity. QSA-26-10 (published June 17, 2026) bundled 18 CVEs across QTS 5.2.7, QuTS hero h5.2.8, QuTS cloud and QVP — including command-injection and memory-corruption bugs — but QNAP's own page rates the overall advisory "Important," not Critical, despite some press coverage calling it that; fixed builds are QTS 5.2.9.3499 and QuTS hero h5.2.9. The same day, QNAP published QSA-26-35, rated Critical, covering unauthenticated access flaws in its QuMagie photo app and License Center (CVE-2026-26236, CVE-2026-26237, CVE-2026-44083), fixed in QuMagie 2.9.1/2.10.0 and License Center 1.9.56. None of QNAP's 2026 advisories have reached CISA's KEV catalog as of this writing. QNAP launched its own Security Bounty Program in 2023, paying up to $20,000 for OS-level reports, $10,000 for applications, and $5,000 for cloud services; QNAP has said the program logged 224 submitted reports and roughly $88,000 in paid rewards through late 2025.

Synology DSM vs QNAP QTS: security feature comparison

CategorySynology DSMQNAP QTS / QuTS hero
Active CISA KEV entries (2026)1 (CVE-2024-10441, added Nov. 18, 2026)0
Historical KEV entries1 total12 total (all 2022–2023)
Most recent Critical advisorySynology-SA-26:19, Nov. 13, 2026 (CVSS 9.8)QSA-26-35, June 17, 2026 (Critical, no published CVSS)
Bug bounty — max OS payoutUp to $30,000 (PSIRT, since 2016)Up to $20,000 (since Feb. 2023)
Ransomware campaigns historically targetedNo KEV-listed ransomware campaign on recordDeadBolt, Qlocker (2021–2022, per QSA-22-19 and related advisories)
Public advisory numberingSynology-SA-YY:NN, per-CVE CVSS publishedQSA-YY-NN, severity tier published, CVSS not always listed

Patch cadence and advisory transparency

Both vendors publish per-advisory CVE lists, affected-version tables and fixed-build numbers, which is more than many consumer IoT vendors do. Synology's advisories consistently publish a numeric CVSS 3.1 score per CVE, which makes it easier to triage which fix is urgent. QNAP's advisory pages tend to assign a single severity word ("Critical," "Important," "Low") to the whole bundle rather than a per-CVE score, which occasionally creates the kind of press-vs-vendor severity disagreement seen with QSA-26-10. Neither company publishes a public, machine-readable KEV-style "known exploited" flag of its own — that information only shows up after CISA (or another national CERT) adds an entry, which is part of why this week's Synology listing is notable: it's an independent, third-party confirmation of real-world exploitation, not a vendor self-report. For admins triaging a pile of advisories, that distinction matters more than the raw CVE count: a dozen "Important" CVEs patched before anyone weaponizes them is a very different risk than one CVE that CISA has confirmed is already in active use against live targets, regardless of which vendor shipped the fix first.

Vulnerability disclosure: who pays more, who moves faster

On paper, Synology's bounty ceiling is higher ($30,000 vs. QNAP's $20,000 for OS-level bugs), and its program has run a decade longer. QNAP's younger program has nonetheless generated a steady publication pipeline — 224 reports and roughly $88,000 paid out by its own count through late 2025 — and QNAP maintains a separate Coordinated Vulnerability Disclosure policy for reports outside bounty scope. Both companies' bounty terms exclude denial-of-service testing, require reproducible proof-of-concept code, and reserve the right to change program terms without notice — standard clauses, not red flags. Response-time commitments differ: Synology's bounty page says its security team replies within seven days of a report, while QNAP routes non-bounty reports through a separate Coordinated Vulnerability Disclosure policy rather than a single unified intake form. Neither company's program guarantees a specific patch-release timeline once a bug is confirmed — both reserve discretion over when and how a fix ships, which is standard in the industry but worth knowing before assuming a "reported" bug equals an "imminently patched" one.

The ransomware history gap

The single biggest asterisk on QNAP's record, and the thing most "which NAS is safer" debates actually revolve around, isn't a CVE count — it's that QNAP devices were the preferred target of consumer NAS ransomware for several years running. DeadBolt and Qlocker both hit QTS devices that had automatic port-forwarding or UPnP enabled and were running outdated QTS 4.2–4.4.x builds and bundled apps, per QNAP's own QSA-22-19 advisory cited above. That same advisory notes QTS 4.5.x, 5.x, and QuTS hero h4.5.x/h5.x were unaffected as long as their bundled App Center applications were also kept current — the ransomware wave tracked stale firmware and exposed ports, not a single structural flaw in QTS itself. Synology has no equivalent KEV-listed or vendor-confirmed mass-ransomware campaign on record. That history is a real mark against QNAP's exposure in the 2021–2023 window, but it's also largely a story about internet-exposed, unpatched devices rather than about QTS being structurally weaker than DSM — the same failure mode (auto port-forwarding plus stale firmware) would be just as dangerous on a neglected Synology box.

Verdict: which is more secure in 2026?

Neither OS has a clean sheet, and "more secure" depends on what you're weighting. If the metric is current, confirmed active exploitation, Synology is the one in the headlines this week, with its first-ever KEV entry and a due date of November 21. If the metric is multi-year KEV exposure and ransomware history, QNAP's 2021–2023 record is heavier, even though it's gone quiet since. If the metric is bounty generosity and advisory transparency, Synology's higher payout ceiling and per-CVE CVSS scoring edge it ahead. The honest read: both vendors ship dozens of CVEs a year, both have had critical, pre-auth bugs reach KEV status at some point, and the single biggest controllable risk factor for either platform isn't the vendor — it's whether the device is reachable from the open internet with auto-updates and 2FA turned off. Treat this as a wash on raw security engineering and a win for whichever vendor you can actually keep current. Buyers choosing between the two for a new deployment in 2026 should weigh this comparison alongside ordinary purchase factors — app ecosystem, hardware cost, RAID tooling — rather than treating either vendor's current advisory count as a tie-breaker on its own; both have shipped, and fixed, critical pre-authentication bugs this year, and both will likely do so again before 2027.

If you run either platform, do this before Friday:
  • Synology DSM/BeeStation: confirm you're on DSM 7.2.2-72806-1 or later (or the equivalent 7.1/7.2/6.2 build) to close CVE-2024-10441 ahead of the Nov. 21 KEV deadline, then also apply the Nov. 13 SA-26:19 update.
  • QNAP QTS/QuTS hero: update to QTS 5.2.9.3499 / QuTS hero h5.2.9 or later to close the QSA-26-10 bundle, and update QuMagie/License Center for QSA-26-35.
  • On both platforms: disable automatic router port-forwarding/UPnP for the NAS admin interface, enable two-factor authentication, and put remote access behind a VPN or the vendor's reverse-proxy/VPN tooling rather than exposing DSM or QTS directly to the internet.

What's next

The near-term test is whether Synology's CVE-2024-10441 stays a one-off KEV entry or is followed by one of this month's new Critical bugs (CVE-2026-76954 or CVE-2026-85101) if active exploitation is later confirmed. On the QNAP side, the question is whether QSA-26-10 and QSA-26-35 — both from mid-2026 — stay clean of KEV status the way QTS 5.x has for the past three years, or whether a wave of unpatched QTS 5.2.7 boxes eventually draws the same scrutiny QTS 4.x did in 2022. Either way, the November 21 deadline is the immediate action item for Synology admins, and a reminder that NAS boxes — regardless of brand — remain high-value, frequently internet-exposed targets that need the same patch discipline as any edge device. For broader context on how perimeter defenses factor into NAS exposure, see our explainer on how a firewall screens inbound traffic and our comparison of next-gen firewall platforms that many NAS admins put in front of these devices.

Frequently asked questions

What is CVE-2024-10441 and why is it in the news in November 2026?

CVE-2024-10441 is a critical (CVSS 9.8) remote-code-execution flaw in the system plugin daemon used by Synology DSM and BeeStation OS. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on November 18, 2026, confirming it is being actively exploited, and set a patch deadline of November 21, 2026 for federal civilian agencies.

Which DSM versions are affected by CVE-2024-10441, and what's the fix?

Per Synology's advisory Synology-SA-24:20, fixed builds have been available since 2024: DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, and 7.1.1-42962-7, plus DSM 6.2.4-25556-8 and BeeStation OS 1.1-65374. Anyone still on an earlier build should update immediately.

Has QNAP QTS ever had a CISA KEV-listed vulnerability?

Yes — CISA's KEV catalog lists 12 QNAP entries, all dated 2022–2023, tied to Photo Station, File Station and NAS command-injection flaws exploited during the DeadBolt and Qlocker ransomware waves. No QNAP CVE has been added to KEV since 2023, and QTS 5.2.x has no KEV-listed entries to date.

Is Synology DSM or QNAP QTS more secure overall?

Neither has a clean record. Synology just received its first-ever KEV listing and is mid-way through its heaviest 2026 patch cycle, including two Critical CVEs in Synology-SA-26:19 (CVSS 9.8 and 8.6). QNAP has a heavier historical KEV tail from 2021–2023 but nothing added since, plus a 2026 Critical advisory (QSA-26-35) and an 18-CVE Important bundle (QSA-26-10). Security engineering looks roughly comparable; exposure and patch discipline on each individual device matter more than the vendor.

Which vendor pays more through its bug bounty program?

Synology's Security Bug Bounty Program pays up to $30,000 for operating-system vulnerabilities and has run since 2016 under its PSIRT team. QNAP's Security Bounty Program, launched in 2023, pays up to $20,000 for OS-level reports and has logged roughly 224 submitted reports and $88,000 in rewards through late 2025, per QNAP's own figures.

What should NAS owners do right now?

Synology users should update past DSM 7.2.2-72806-1 (or the equivalent build on their branch) to close CVE-2024-10441 before the November 21, 2026 KEV deadline, then apply the November 13 Synology-SA-26:19 update. QNAP users should move to QTS 5.2.9.3499 / QuTS hero h5.2.9 or later for the QSA-26-10 bundle. On either platform, disable UPnP/automatic port-forwarding for the admin interface, enable two-factor authentication, and avoid exposing the NAS directly to the internet.

Sources

More on NAS Security →Synology DSMQNAP QTSNAS SecurityCISA KEVComparison
Sana Qureshi
Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Security & Privacy

See all