No advisories yet.
Solution
Upgrade to PeaZip 11.3.0 or higher. The fix sanitizes the archive entry name used to build the executed path (sanitizenamestr, stripping ../ and ..\ sequences) and enforces that the resolved path stays inside the extraction directory (sanitizepath, via ExpandFileName containment) in execute_obj, and extends the dangerous-extension check to the "Open/Preview with associated application" route, not only the double-click event. Fix commit 009fc35 (2026-09-03).
Workaround
No workaround given by the vendor.
Thu, 15 Oct 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 15 Oct 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Path Traversal (CWE-22) in the execute_obj function of the archive object viewer (peach.pas) in PeaZip 11.2.0 and earlier on Windows allows an attacker who convinces a victim to preview an entry of a crafted archive via the "Preview with... -> Associated application" action (Shift+Ctrl+O) to execute an arbitrary program already present on the victim's system, with no warning dialog. The function validates only outname (PeaZip's own temporary directory) with checkfiledirname, while the string actually executed is the concatenation outname+tempstring; tempstring is taken verbatim from the archive entry name (StringGridList.Cells[12,...]) and is never validated. checkfiledirname (list_utils.pas) rejects control and reserved characters in the file name but performs no ".." path-containment check, so an entry named ../../../../Windows/System32/calc.exe escapes the extraction directory and is passed to cp_open -> ShellExecuteW; the extracting backend (7-Zip) strips the traversal while the opener does not. In addition, the SECEXTCONST dangerous-extension confirmation prompt is implemented only in the double-click handler (grid_obj_open) and not on this preview route, so an executable inside an archive reaches ShellExecuteW unannounced, and where the prompt does fire it names the entry's display name rather than the resolved path that will run. Arbitrary code execution was demonstrated with a proof of concept against official PeaZip builds, confirmed on two archive formats (.zip and .tar) to show the defect is in PeaZip's own path handling and not in a single format parser. | |
| Title | Path traversal in PeaZip object preview allows execution of arbitrary programs via a crafted archive entry name | |
| First Time appeared |
Peazip
Peazip peazip |
|
| Weaknesses | CWE-22 CWE-693 |
|
| CPEs | cpe:2.3:a:peazip:peazip:*:*:*:*:*:*:windows:*:* | |
| Vendors & Products |
Peazip
Peazip peazip |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Secur0
Published:
Updated: 2026-10-15T13:11:13.654Z
Reserved: 2026-10-01T17:09:25.587Z
Link: CVE-2026-104025
Updated: 2026-10-15T13:11:10.013Z
Status : Received
Published: 2026-10-15T13:17:10.617
Modified: 2026-10-15T14:17:13.717
Link: CVE-2026-104025
No data.
OpenCVE Enrichment
No data.