CVE-2024-5401VulnerabilityPublished 4 Dec 2025

CVE-2024-5401: Synology DiskStation Manager (DSM) · Improper Control of Dynamically-Managed Code Resources

Affects Synology DiskStation Manager (DSM)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 7.2.1-69057-2 or 7.1.1-42962-8 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.2.1-69057-2, 7.1.1-42962-8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade synology/dsm to 7.2.1-69057-2 or 7.1.1-42962-8.

Affected software

Product	Affected	Fixed in
Synologysynology/dsm`pkg:rpm/synology/dsm`Other threats	Affected <7.1.1-42962-8 <7.2.1-69057-2 =7.2.1 =7.2.2	Fixed in 7.1.1-42962-8 7.2.1-69057-2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately update Synology DSM to versions 7.1.1-42962-8, 7.2.1-69057-2, 7.2.2-72806 or later, and DSMUC to version 3.1.4-23079 or later, as these contain patches addressing the vulnerability. 2. Restrict access to DSM management interfaces to trusted internal networks or VPNs to reduce exposure to authenticated attackers. 3. Enforce strong authentication policies, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 4. Regularly audit user accounts and privileges on Synology devices to ensure minimal necessary access and promptly remove unused or suspicious accounts. 5. Monitor DSM logs for unusual privilege escalation attempts or anomalous activities indicative of exploitation attempts. 6. Implement network segmentation to isolate NAS devices from general user networks where possible. 7. Educate users about the risks of credential sharing and phishing attacks that could lead to unauthorized authentication. 8. Consider deploying endpoint detection and response (EDR) solutions to detect suspicious behavior on NAS devices. These steps go beyond generic advice by focusing on access control, authentication hardening, and proactive monitoring tailored to the Synology DSM environment.

Description

Improper control of dynamically-managed code resources vulnerability in WebAPI component in Synology DiskStation Manager (DSM) before 7.1.1-42962-8 and 7.2.1-69057-2 and 7.2.2-72806 and Synology Unified Controller (DSMUC) before 3.1.4-23079 allows remote authenticated users to obtain privileges without consent via unspecified vectors.

Impact

For European organizations, this vulnerability could lead to unauthorized privilege escalation on Synology NAS devices, potentially allowing attackers with valid credentials to alter system configurations, deploy malicious code, or interfere with data integrity. While confidentiality and availability are not directly impacted, integrity compromises could facilitate further attacks, data tampering, or persistence mechanisms. Organizations using Synology DSM in multi-user environments or with exposed management interfaces are particularly at risk. Given the widespread use of Synology NAS in European SMBs, enterprises, and public sector entities for file storage, backup, and application hosting, exploitation could disrupt business operations or lead to compliance issues under regulations such as GDPR if data integrity is compromised. The requirement for authentication limits exposure but does not eliminate risk, especially in cases of credential compromise or insider threats. The lack of known exploits in the wild reduces immediate risk but underscores the importance of proactive patching and access control.

References

synology.com/en-global/security/advisory/Synology_SA_24_27 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Dec 2025, 14:46 UTC

Technical details

References

Community reviews

Related threats