Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-3179: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ASUSTOR ADM

0
Critical
VulnerabilityCVE-2026-3179cvecve-2026-3179cwe-22
Published: Wed Feb 25 2026 (02/25/2026, 05:55:07 UTC)
Source: CVE Database V5
Vendor/Project: ASUSTOR
Product: ADM

Description

CVE-2026-3179 is a critical path traversal vulnerability in ASUSTOR ADM's FTP Backup feature. The vulnerability arises because the ADM does not properly sanitize filenames received from FTP servers, allowing malicious filenames with path traversal sequences. Exploiting this flaw, an attacker or a man-in-the-middle (MITM) can cause the system to write files outside the intended backup directory, potentially overwriting arbitrary files. This can lead to privilege escalation or remote code execution without requiring authentication or user interaction. The affected versions range from ADM 4. 1. 0 through 4. 3. 3. ROF1 and 5.

AI-Powered Analysis

AILast updated: 02/25/2026, 06:55:48 UTC

Technical Analysis

CVE-2026-3179 is a path traversal vulnerability classified under CWE-22 affecting ASUSTOR ADM's FTP Backup functionality. The vulnerability occurs because the ADM software fails to properly sanitize or validate filenames received from FTP servers when parsing directory listings. Specifically, an attacker controlling the FTP server or positioned as a man-in-the-middle can craft filenames containing path traversal sequences such as '../' that cause the ADM client to write files outside the designated backup directory. This improper limitation of pathname allows an attacker to overwrite arbitrary files on the system, potentially including critical system files or configuration files. The consequences of such overwriting include privilege escalation, where the attacker gains higher system privileges, or remote code execution, enabling full system compromise. The vulnerability affects ADM versions from 4.1.0 through 4.3.3.ROF1 and 5.0.0 through 5.1.2.RE51. The CVSS v4.0 score of 9.2 reflects the vulnerability's critical nature due to its network attack vector, low attack complexity, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the vulnerability's characteristics make it a high-risk target for attackers. The lack of patch links suggests that fixes may not yet be publicly available, emphasizing the need for immediate mitigation.

Potential Impact

The impact of CVE-2026-3179 is severe for organizations using vulnerable ASUSTOR ADM versions. Successful exploitation can lead to arbitrary file overwriting, which may corrupt or replace critical system files, backup data, or security configurations. This can cause system instability, data loss, or denial of service. More critically, attackers can leverage this to escalate privileges or execute arbitrary code remotely, potentially gaining full control over the affected NAS device. Given that ASUSTOR ADM is often used in enterprise and SMB environments for network-attached storage and backup, compromise can lead to exposure or loss of sensitive corporate data, disruption of business operations, and lateral movement within internal networks. The vulnerability’s exploitation does not require authentication or user interaction, increasing the risk of automated or widespread attacks. Organizations relying on ASUSTOR ADM for backup and storage must consider this a critical threat that can undermine data integrity and system security.

Mitigation Recommendations

To mitigate CVE-2026-3179, organizations should immediately verify if their ASUSTOR ADM installations fall within the affected version ranges (4.1.0 to 4.3.3.ROF1 and 5.0.0 to 5.1.2.RE51). If patches or updates are released by ASUSTOR, they should be applied without delay. In the absence of official patches, organizations should consider disabling the FTP Backup feature or restricting FTP backup operations to trusted, internal FTP servers only, eliminating exposure to malicious or MITM FTP servers. Network segmentation and firewall rules should be employed to limit FTP traffic to known safe sources. Additionally, monitoring file system changes and backup directories for unexpected modifications can help detect exploitation attempts. Employing secure FTP alternatives (e.g., SFTP or FTPS) with strong authentication and encryption can reduce the risk of MITM attacks. Finally, organizations should conduct regular security audits and maintain up-to-date backups stored offline or in immutable storage to recover from potential compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
ASUSTOR1
Date Reserved
2026-02-25T03:47:42.339Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699e999bb7ef31ef0be231a6

Added to database: 2/25/2026, 6:41:31 AM

Last enriched: 2/25/2026, 6:55:48 AM

Last updated: 2/25/2026, 8:59:11 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats