Quick answers
- Is CVE-2026-104024 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104024 being exploited in the wild.
- How severe is CVE-2026-104024?
- Informational severity, published 15 October 2026.
- Which products and versions are affected?
- PeaZip 10.5.0 through 11.2.0 on Windows.
- Is there a fix for CVE-2026-104024?
- 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-104024 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-104024?
- 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
The vulnerability is an incomplete allowlist (CWE-184) in the dangerous-extension confirmation logic (peach.pas, grid_obj_open). The check uses exact string comparison against a hardcoded list of seven extensions (exe, cmd, msi, bat, ps1, vbs, reg), missing shell-executable types like .url and .lnk that Windows will execute via ShellExecuteW. A .url entry with attacker-controlled URL launches without prompting; a .lnk entry can execute arbitrary commands with arguments, including UNC paths for remote payload delivery.
Affected products
- PeaZip PeaZip 10.5.0 through 11.2.0 on Windows
Timeline
- 2026-10-15: disclosed