CVE-2024-10441: Critical Synology RCE
Active exploitation confirmed in CISA KEV.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HActive exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-18. Federal agencies must patch by 2026-11-21.
TL;DR - CVE-2024-10441 is a CVSS 9.8 remote arbitrary-code-execution flaw in Synology’s system plugin daemon. - BeeStation OS/BSM and several DSM release branches are affected; fixed builds are available. - CISA added the CVE to KEV on 2026-11-18, confirming exploitation in the wild. Patch and investigate exposed systems immediately.
Summary
CVE-2024-10441 is a critical Synology vulnerability involving improper output encoding or escaping in the system plugin daemon used by Synology BeeStation OS, also called BeeStation Manager (BSM), and DiskStation Manager (DSM). Synology and NVD describe the issue as allowing remote attackers to execute arbitrary code through unspecified vectors.
The vulnerability is especially serious for systems reachable from untrusted networks. The published CVSS vector requires no authentication, no user interaction, and only network access. Successful exploitation can affect confidentiality, integrity, and availability, allowing a compromised NAS to expose stored files, alter configurations, disrupt backups, or provide a foothold for further intrusion.
For broader vulnerability-management context, see the CVE-2026-18602 analysis.
| Field | Detail |
|---|---|
| CVE ID | CVE-2024-10441 |
| CVSS | 9.8 Critical, CVSS v3.1 |
| Attack vector | Network |
| Authentication / privileges | None required |
| User interaction | None required |
| Impact | Remote arbitrary code execution |
| Patch available | Yes |
| Exploitation status | Confirmed exploited in the wild through CISA KEV listing |
Treat this as an incident-prevention priority rather than a routine appliance update. Inventory and patch internet-facing DSM or BeeStation systems first. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on 2026-11-18, with a federal remediation due date of 2026-11-21.
Analyst’s Take: Patch exposed systems first, then investigate them as potentially compromised rather than waiting for a confirmed alert. The lack of a public exploit signature makes version, exposure, and behavioral telemetry more useful than a narrow payload search. CISA’s KEV listing means exploitation is confirmed, even though the available sources do not identify a threat actor or campaign.
Root Cause
The root cause is improper encoding or escaping of output in Synology’s system plugin daemon. Data handled by the daemon is not sufficiently encoded or escaped before being used by a downstream operation. The available public descriptions do not identify the precise request format, vulnerable function, or complete exploitation sequence.
That lack of implementation detail does not reduce the operational risk. A remote attacker can reportedly reach the vulnerable functionality without authentication, and successful exploitation leads to arbitrary code execution. Defenders should therefore assume that a vulnerable, reachable device could be fully controlled at the appliance level rather than merely exposed to information disclosure.
Synology credits Pumpkin Chang and Orange Tsai of the DEVCORE Research Team, Ryan Emmons, and Team Smoking Barrels with discovering or reporting the issue. The public advisory material identifies the vulnerable daemon and fixed release branches but does not provide enough technical detail to construct a reliable detection signature from the root cause alone.
Technical Notes
The public CVE description characterizes the issue as follows:
Improper encoding or escaping of output vulnerability in the system plugin daemon … allows remote attackers to execute arbitrary code via unspecified vectors.
Because the vulnerable request path is unspecified, organizations should avoid relying on a single URL, payload, or regular expression. Detection should combine DSM audit events, authentication records, package activity, process telemetry, filesystem monitoring, and network-flow data.
Who’s Exposed
The affected products are Synology BeeStation OS/BeeStation Manager and DiskStation Manager. The following release branches and versions are identified as affected:
| Product | Affected versions | Fixed version |
|---|---|---|
| BeeStation OS / BSM | 1.0; 1.1 versions before 1.1-65374 | 1.1-65374 or later |
| DSM 7.2 | Versions before 7.2-64570-4 | 7.2-64570-4 or later |
| DSM 7.2.1 | Versions before 7.2.1-69057-6 | 7.2.1-69057-6 or later |
| DSM 7.2.2 | Versions before 7.2.2-72806-1 | 7.2.2-72806-1 or later |
| DSM 7.1 | Versions below 7.1.1-42962-7, as identified in affected-product data | 7.1.1-42962-7 or later |
| DSM below 7.0 | Status is unknown in the available NVD product data | Follow current Synology support and upgrade guidance |
DSM versions below 7.0 require particular care because the available affected-product data does not establish a definitive vulnerable or non-vulnerable status. Treat unsupported or indeterminate systems as higher risk: restrict their network access, confirm whether Synology provides a supported upgrade, and avoid exposing administration services directly to the internet.
Exposure depends on more than the installed version. A device behind a firewall may still be reachable through port forwarding, reverse proxies, remote-management services, VPN misconfiguration, or cloud-mediated access paths. Inventory directly internet-facing systems and appliances accessible from untrusted internal segments.
Severity Breakdown
CVE-2024-10441 has a CVSS v3.1 base score of 9.8 Critical with the following vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Component | Value | Operational meaning |
|---|---|---|
| Attack Vector | Network | Exploitation can occur over a network connection |
| Attack Complexity | Low | No unusual conditions are required |
| Privileges Required | None | An unauthenticated attacker can attempt exploitation |
| User Interaction | None | No victim action is required |
| Scope | Unchanged | Impact remains within the vulnerable security authority |
| Confidentiality | High | Attackers may read protected data |
| Integrity | High | Attackers may modify data or configuration |
| Availability | High | Attackers may disrupt services or render data inaccessible |
The score reflects remote reachability combined with unauthenticated access. For a storage appliance, the high confidentiality and integrity ratings are particularly consequential because NAS systems commonly contain business documents, credentials, backups, media, and synchronization data.
CVSS does not measure whether a particular organization has exposed a device, maintains good segmentation, or has reliable backups. Those environmental factors can reduce or increase practical risk. CISA KEV status establishes that exploitation is not merely theoretical, so defenders should prioritize the vulnerability independently of the base score’s limitations.
Exploitation Status
Exploitation in the wild is confirmed. CISA added CVE-2024-10441 to the Known Exploited Vulnerabilities catalog on 2026-11-18. KEV inclusion is the authoritative basis for stating that real-world exploitation has occurred. CISA lists the federal remediation due date as 2026-11-21.
CISA currently identifies known ransomware campaign use as unknown. KEV status does not identify a particular threat actor, ransomware family, campaign, or intrusion set. Organizations should not infer ransomware involvement solely from the KEV listing.
The status of a public proof of concept requires qualification. Third-party aggregators make conflicting claims, but no authoritative public GitHub repository or vendor-published exploit reference was independently verified in the supplied research. No specific public PoC is asserted here. Defenders should assume exploit knowledge may exist among attackers even if a public, reproducible PoC cannot be confirmed.
Related Reading
Sources
The primary sources for this assessment are Synology security advisories SA-24-20 and SA-24-23:
The NVD record provides the CVE description, affected product configurations, CVSS v3.1 score, and vector:
CISA’s Known Exploited Vulnerabilities catalog confirms exploitation in the wild and records the catalog date and remediation deadline:
These sources establish the vulnerability, affected branches, fixed builds, severity, and exploitation status. They do not provide a verified public exploit repository or a complete exploit-request signature. Detection and response programs should therefore combine version validation, exposure review, behavioral telemetry, and forensic investigation rather than depend on a presumed exploit pattern.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.
Detection Guidance
Begin with asset and exposure validation. Identify every BeeStation and DSM host, record its installed build, map internet-facing addresses and forwarded ports, and determine whether administration interfaces are reachable from untrusted networks. A vulnerable version with no observed suspicious activity still requires patching because the absence of logs is not evidence that exploitation did not occur.
Review authentication and administrative activity around each exposed host. Look for unexpected administrator logins, new accounts, privilege changes, package installations, configuration changes, scheduled tasks, and processes that do not match the device’s normal workload. Inspect outbound connections from the NAS as well, especially connections to unfamiliar public addresses, command-and-control infrastructure, file-sharing services, or remote administration endpoints.
Technical Notes
The precise exploit request is publicly unspecified, so there is no reliable single network signature to deploy. Use telemetry-based searches such as the following generic Splunk-style query, adapting field names to the local DSM log pipeline:
index=nas
(host_type="Synology" OR product="DSM" OR product="BeeStation")
(
action IN ("login_success","account_created","privilege_changed",
"package_installed","task_created","config_changed")
OR process IN ("sh","bash","wget","curl","nc","socat","python","perl")
)
| stats count values(action) as actions values(process) as processes
values(src_ip) as source_ips values(dest_ip) as destination_ips
by host user
The query is intentionally behavior-oriented rather than exploit-specific. Prioritize events involving previously unseen source addresses, administrative accounts, unexpected shells or interpreters, new scheduled tasks, package activity outside approved maintenance windows, and outbound connections initiated by a storage appliance.
For network monitoring, alert on public exposure and unusual management traffic first. Compare current firewall and NAT rules against the approved baseline, and review reverse-proxy access logs for repeated requests to DSM or plugin-related endpoints. Because the vulnerable path is unspecified, do not treat a clean URI-based search as a conclusive negative finding.
Remediation Steps
Upgrade each affected product branch to the corresponding fixed build or, preferably, the latest vendor-supported release:
- BeeStation OS/BSM: 1.1-65374 or later
- DSM 7.2: 7.2-64570-4 or later
- DSM 7.2.1: 7.2.1-69057-6 or later
- DSM 7.2.2: 7.2.2-72806-1 or later
- DSM 7.1: 7.1.1-42962-7 or later, where applicable and supported
Do not stop at the historical minimum if Synology offers a newer supported update. After updating, verify the installed build from the DSM or BeeStation management interface and record the result in the asset inventory. If an update cannot be applied immediately, remove direct internet exposure, restrict management access to a trusted administration network, and apply firewall controls that limit access to known management sources.
Technical Notes
Use the Synology management interface to install the appropriate update. For DSM, the administrative workflow is generally:
- Open Control Panel.
- Select Update & Restore.
- Check for updates or upload the vendor-provided update package.
- Confirm the installed version after reboot.
For BeeStation, use the supported update mechanism in the BeeStation administration interface and verify that the system reports 1.1-65374 or later. Exact command-line update syntax is not provided in the vendor material supplied for this CVE; administrators should not substitute an unverified shell command for the supported update workflow.
Until patching is complete, enforce compensating controls such as:
- Remove port forwarding for DSM and BeeStation administration services.
- Restrict access through a trusted management network or jump host.
- Block inbound access from the public internet at the edge firewall.
- Segment NAS systems from user workstations and sensitive server networks.
- Disable unnecessary remote-management exposure.
- Increase logging and preserve relevant evidence before rebuilding a suspected compromise.
If compromise is suspected, preserve logs and volatile evidence where feasible before resetting or rebuilding the appliance. Rotate administrative passwords, API tokens, stored credentials, and other secrets that may have been accessible from the device. Review backup integrity before relying on backups for recovery, and investigate unexpected file changes, encryption activity, deleted snapshots, and newly created accounts.