CVE-2026-104025
Description
A flaw was found in PeaZip. This vulnerability allows an attacker to achieve arbitrary code execution by convincing a user to preview an entry within a specially crafted archive file. Because the archive preview functionality does not properly sanitize file paths against directory traversal sequences, the application can launch an arbitrary program already present on the victim's system without displaying a security warning.
Statement
This vulnerability is rated as having an Important impact because enticing a user to preview an entry in a manipulated archive could result in arbitrary code execution with the permissions of the logged-in user. However, PeaZip is neither shipped nor supported in Red Hat Enterprise Linux or any other Red Hat enterprise products. Additionally, the flaw relies on Windows-specific program execution handlers, meaning standard Linux environments are not vulnerable.
Mitigation
Avoid using the "Preview with... -> Associated application" action on entries from untrusted or unknown archives. Instead, fully extract the archive to a directory first and open the extracted files from there: the archive extraction backend used by PeaZip strips path traversal sequences during extraction, so that route is not subject to this preview flaw. Users of the Fedora PeaZip package should also install updated packages once the community releases the fix.
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 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.
