CISA Adds Synology DSM Flaw to KEV Catalog, Patch by Nov. 21

The flaw lets remote attackers run arbitrary code on DSM and BeeStation OS with no user interaction. Synology patched it in 2024 — CISA now confirms active exploitation.

Synology DiskStation NAS device, representing the DSM platform affected by CVE-2024-10441
Product photo courtesy of Synology. Image: Synology.

The Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2024-10441, a critical remote code execution flaw in Synology's DiskStation Manager (DSM), to its Known Exploited Vulnerabilities (KEV) Catalog on November 18, 2026. The advisory gives federal civilian agencies until November 21, 2026 — just three days — to apply Synology's fix or take the affected systems offline, after CISA confirmed the two-year-old bug is now being exploited in the wild.

What Happened

CVE-2024-10441 is not a new discovery. Synology first disclosed it in November 2024 and published full technical details in March 2025 under advisory Synology-SA-24:20, titled "DSM (PWN2OWN 2024)." What changed on November 18, 2026, is CISA's confirmation that the flaw is being actively exploited against real devices, which triggered its addition to the KEV Catalog.

That timing matters. Under CISA's current risk-based remediation directive, Binding Operational Directive (BOD) 26-04, the deadline an agency gets depends on how a flaw scores across four factors: whether the asset is reachable from the internet, whether the CVE is in the KEV Catalog, whether exploitation can be automated, and whether a successful attack hands the intruder full control of the system. CVE-2024-10441 — an unauthenticated, network-reachable, fully automatable path to arbitrary code execution — lands in the most severe tier, which is why the window here is a mere three days rather than the 14-to-30-day windows typical of older KEV entries.

As of this writing, CISA's enrichment data lists knownRansomwareCampaignUse for this entry as "Unknown," meaning there is no confirmed link to a specific ransomware operation. The exploitation CISA is responding to has not been publicly attributed to a named threat actor or campaign; treat any claims about "who" is behind it as unconfirmed until CISA, Synology, or a named incident-response source says otherwise.

What Is Synology DSM, and Why Does It Matter Here

DiskStation Manager (DSM) is the Linux-based operating system that runs on Synology's DiskStation line of network-attached storage (NAS) appliances — the small server boxes that sit in homes, offices, schools, and data centers to centralize file storage, backups, surveillance recording (via Synology's Surveillance Station), and increasingly, lightweight virtualization and container workloads. Synology also ships a consumer-oriented variant called BeeStation, running BeeStation OS (BSM), which shares the vulnerable component with DSM.

Because DSM boxes are purpose-built storage appliances, they often hold an organization's most sensitive data: financial records, surveillance footage, backups of production systems, and in many small-business and home-office deployments, the only copy of that data. A remote code execution flaw in DSM is attractive to attackers precisely because compromising the NAS can mean compromising the backup of last resort, not just another endpoint.

FieldDetail
CVE IDCVE-2024-10441
Vulnerability nameImproper Encoding or Escaping of Output in the system plugin daemon
CVSS v3.1 score9.8 (Critical) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWECWE-116: Improper Encoding or Escaping of Output
VendorSynology
Affected productsDiskStation Manager (DSM) 7.2.2, 7.2.1, 7.2, 7.1; BeeStation OS (BSM)
Fixed versionDSM 7.2.2-72806-1 or later (see full branch table below)
KEV date addedNovember 18, 2026
KEV due dateNovember 21, 2026

How the Flaw Works

Synology's own advisory describes CVE-2024-10441 as an "improper encoding or escaping of output vulnerability in the system plugin daemon" — a background process (sometimes referred to informally as "sysplugin") that handles plugin-related operations on DSM and BeeStation OS. Because output from this daemon isn't properly encoded or escaped before it's used elsewhere, a remote attacker can supply crafted input that gets interpreted as commands rather than data, a classic injection pattern that, per CISA's NVD record, "allows remote attackers to execute arbitrary code via unspecified vectors."

The CVSS 3.1 vector — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — spells out why this rates a 9.8 out of 10: the attack can be launched over the network (AV:N), requires low attack complexity (AC:L), needs no privileges on the target (PR:N) and no action from a user (UI:N), and a successful exploit gives the attacker complete compromise of confidentiality, integrity, and availability. In plain terms, an attacker who can reach a vulnerable DSM or BeeStation device over the network can take full control of it without tricking anyone into clicking anything or needing valid credentials.

The bug traces back to Pwn2Own Ireland 2024, where Synology's advisory credits the finding — grouped with two related issues (one allowing file reads, one allowing an adjacent attacker to write specific files) — to researchers including Pumpkin Chang and Orange Tsai of DEVCORE, Ryan Emmons, and the team "Smoking Barrels." Synology tracked the three related cases separately by Zero Day Initiative case number, with the remote-code-execution path that CISA is now flagging as CVE-2024-10441.

Because Synology's public advisory describes the flaw only at a high level — "unspecified vectors" is the phrase both Synology and NVD use — the precise request or payload an attacker sends isn't published. That's standard practice for a vulnerability originating from a competitive hacking contest: Zero Day Initiative and the vendor typically withhold exploit-level detail even after a patch ships, to avoid handing a ready-made blueprint to attackers who haven't bothered to reverse-engineer the fix themselves. The lack of public proof-of-concept code hasn't stopped exploitation from reportedly occurring now, which underscores that attackers can and do reconstruct working exploits from patch diffs and vendor advisories alone, especially for a two-year-old bug with this much exposure in the wild.

Who Is Affected

Per Synology's advisory and NVD, the vulnerability affects:

  • DSM 7.2.2 — builds before 7.2.2-72806-1 (Critical)
  • DSM 7.2.1 — builds before 7.2.1-69057-6 (Critical)
  • DSM 7.2 — builds before 7.2-64570-4 (Critical)
  • DSM 7.1 — builds before 7.1.1-42962-7 (Critical)
  • DSM 6.2 — builds before 6.2.4-25556-8 (Moderate)
  • BeeStation OS (BSM) — builds before 1.1-65374

In practice, that covers the vast majority of DiskStation NAS units and BeeStation devices that have not been updated since Synology shipped fixes starting in late 2024. Any device left on default auto-update settings for more than a year should already carry a patched build, but devices administered manually, running end-of-support DSM branches, or sitting on isolated/offline networks that rarely check for updates are the ones most likely to still be exposed.

Why CISA Added a Two-Year-Old Bug to KEV Now

It's common for a vulnerability to sit disclosed and patched for months or years before CISA has evidence it's being actively exploited — KEV additions are driven by observed exploitation, not by severity scores alone. CVE-2024-10441 fits that pattern: Synology published fixes across every affected DSM branch between late 2024 and early 2025, well before CISA's November 18, 2026 KEV addition. The gap suggests one of two things, neither mutually exclusive: attackers have been quietly working through the large population of internet-exposed, unpatched DSM and BeeStation devices that never installed the two-year-old fix, or exploitation only recently became prevalent enough, or was only recently detected, for CISA to confirm "known exploited" status. CISA's KEV entry does not specify which, and the agency's public notes point primarily to its own BOD 26-04 guidance rather than incident-specific detail — so treat the precise cause and scale of current in-the-wild activity as unconfirmed beyond the fact that CISA now considers it occurring.

Unpatched, internet-facing NAS appliances are a recurring target for ransomware crews and botnet operators precisely because they're often deployed once and forgotten, unlike laptops and servers that get more routine patch attention. A known, unauthenticated path to full code execution is valuable to attackers for exactly that reason.

Quick take: If you run a Synology DiskStation or BeeStation device and haven't confirmed its DSM/BSM build number in the past year, assume it may be vulnerable until you check. The fix has existed since 2024 — this KEV listing exists because many devices still haven't applied it.

The Three-Day Patch Deadline, Explained

Federal civilian executive branch (FCEB) agencies are bound by CISA's KEV deadlines under BOD 26-04, which replaced the older flat 14-to-21-day KEV remediation windows with a risk-scored model. As CISA outlined when the directive took effect, vulnerabilities that combine internet exposure, KEV status, automatable exploitation, and total system compromise — exactly the profile of CVE-2024-10441 — fall into the directive's most urgent tier, carrying a three-day remediation window rather than the longer timelines applied to lower-risk KEV entries.

CISA's own required-action language for this entry instructs agencies to "apply mitigations in accordance with vendor instructions," comply with BOD 26-04, and, where mitigations aren't available for an internet-exposed, in-scope asset, to discontinue use of the product until it can be remediated. BOD 26-04 legally binds only FCEB agencies — state, local, and private-sector organizations aren't required to comply — but security teams everywhere generally treat KEV additions and their deadlines as a strong signal of real-world urgency worth matching regardless of sector.

How to Patch Synology DSM and BeeStation OS

Synology's advisory lists the exact builds that resolve CVE-2024-10441 for each affected branch:

  • DSM 7.2.2 → upgrade to 7.2.2-72806-1 or later
  • DSM 7.2.1 → upgrade to 7.2.1-69057-6 or later
  • DSM 7.2 → upgrade to 7.2-64570-4 or later
  • DSM 7.1 → upgrade to 7.1.1-42962-7 or later
  • DSM 6.2 → upgrade to 6.2.4-25556-8 or later
  • BeeStation OS (BSM) → upgrade to 1.1-65374 or later

To check and apply the update on a DiskStation device:

  1. Log in to DSM as an administrator.
  2. Open Control Panel > Update & Restore > DSM Update.
  3. Click Check for updates and compare the reported build number against the fixed versions listed above.
  4. If an update is available, apply it and allow the device to restart; verify the new build number afterward under Control Panel > Info Center.
  5. On BeeStation devices, the equivalent check is under the device's Settings app, which should prompt for an available BSM update if one applies.

Devices on DSM 6.2 or earlier that cannot reach 6.2.4-25556-8 or later, and any hardware whose DSM branch is past Synology's support window entirely, should not be exposed directly to the internet. Where immediate patching isn't possible, administrators should at minimum disable any external/WAN access to DSM's management interfaces and restrict access to a VPN or local network until the update can be applied.

What to Do Next

Whether or not your organization is bound by CISA's directive, the practical steps are the same:

  1. Inventory every Synology DiskStation and BeeStation device you operate, including ones managed by other teams, branch offices, or contractors — unmanaged NAS boxes are the most common source of this kind of exposure.
  2. Check each device's DSM or BSM build number against the fixed versions above, and patch immediately if it's below the applicable threshold.
  3. Audit internet exposure. Confirm DSM's management ports and QuickConnect/remote-access features aren't unnecessarily reachable from the open internet; put remote administration behind a VPN wherever feasible.
  4. Review access and admin logs on any device that was running an unpatched build with internet exposure, looking for unfamiliar logins, new admin accounts, or unexpected scheduled tasks or plugins.
  5. If you suspect compromise, isolate the device from the network before further investigation, and treat any backups stored on it as potentially untrustworthy until verified.
  6. Turn on automatic DSM updates going forward, under Control Panel > Update & Restore, so that future critical security fixes install without relying on someone remembering to check manually.

For the broader incident-response playbook if a NAS or any other system turns out to have been compromised, see our step-by-step guide to what to do after a data breach. This is also the latest in a steady run of KEV additions carrying compressed federal deadlines under the new directive — see our coverage of the Cisco BroadWorks XXE flaw added to KEV and the Perforce Puppet Enterprise flaw added to KEV for how similar deadlines have played out in recent weeks.

Frequently asked questions

What is CVE-2024-10441?

CVE-2024-10441 is a critical (CVSS 9.8) vulnerability in the system plugin daemon of Synology DiskStation Manager (DSM) and BeeStation OS (BSM). Improper encoding or escaping of output lets a remote, unauthenticated attacker execute arbitrary code on the device with no user interaction required.

Why did CISA add a vulnerability from 2024 to the KEV catalog in November 2026?

KEV additions are driven by evidence of active exploitation, not just severity. Synology patched this flaw starting in late 2024, but CISA added it to the Known Exploited Vulnerabilities catalog on November 18, 2026 after confirming it is now being exploited in the wild, likely against devices that never installed the fix.

Which Synology DSM versions are affected?

DSM 7.2.2 before build 7.2.2-72806-1, DSM 7.2.1 before 7.2.1-69057-6, DSM 7.2 before 7.2-64570-4, DSM 7.1 before 7.1.1-42962-7, DSM 6.2 before 6.2.4-25556-8, and BeeStation OS (BSM) before 1.1-65374 are all affected, per Synology's advisory Synology-SA-24:20.

How do I patch Synology DSM against CVE-2024-10441?

In DSM, go to Control Panel > Update & Restore > DSM Update, click Check for updates, and install any available update so the device is running the fixed build for its branch (for example, 7.2.2-72806-1 or later on the 7.2.2 branch). BeeStation users should check for updates in the device's Settings app.

What is the CISA KEV patch deadline for this flaw?

CISA added CVE-2024-10441 to the KEV catalog on November 18, 2026, with a due date of November 21, 2026. Under Binding Operational Directive (BOD) 26-04, federal civilian agencies must remediate or mitigate it, or discontinue use of affected internet-exposed assets, by that date.

Is CVE-2024-10441 linked to a ransomware campaign?

CISA's KEV catalog entry lists knownRansomwareCampaignUse as "Unknown" for this CVE, meaning there is no confirmed link to a named ransomware operation at this time.

Sources

More on Synology DSM →SynologyCISAKEV CatalogNAS SecurityVulnerabilityDSM
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