Quick answers
- Is CVE-2026-104025 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104025 being exploited in the wild.
- How severe is CVE-2026-104025?
- Informational severity, published 15 October 2026.
- Which products and versions are affected?
- PeaZip 11.2.0 and earlier.
- Is there a fix for CVE-2026-104025?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-104025 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-104025?
- Check whether you run PeaZip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the execute_obj function (peach.pas) where the file path is constructed by concatenating a validated temporary directory (outname) with an unvalidated archive entry name (tempstring). While the 7-Zip backend strips traversal sequences during extraction, the execute_obj function passes the concatenated path directly to ShellExecuteW, bypassing the extraction directory containment. Additionally, the dangerous-file extension confirmation prompt (SECEXTCONST) is not implemented on this preview route, allowing executables to reach ShellExecuteW without user notification.
Affected products
- PeaZip PeaZip 11.2.0 and earlier
Timeline
- 2026-10-15: disclosed