CVE-2026-110231
Description
A flaw was found in muCommander. An attacker can exploit this vulnerability to perform an arbitrary file write outside the designated target directory. By convincing a user to extract a specially crafted archive containing directory traversal sequences to a remote server using File Transfer Protocol (FTP) or SSH File Transfer Protocol (SFTP), unnormalized paths bypass extraction validation checks. Consequently, an attacker can create or overwrite files accessible to the user's remote account.
Statement
Red Hat has evaluated this issue as having a Moderate severity impact because successful exploitation requires user interaction to extract an untrusted archive into an active remote session and is constrained by the privileges of the remote user account. Additionally, arbitrary file creation is restricted to the permissions of the targeted remote endpoint rather than enabling local system compromise or elevation of privilege. muCommander is not distributed or supported within Red Hat Enterprise Linux or other Red Hat product portfolios, resulting in no direct impact on default deployments.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
