Quick answers
- Is CVE-2026-105050 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105050 being exploited in the wild.
- How severe is CVE-2026-105050?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- PeaZip before 11.3.0.
- Is there a fix for CVE-2026-105050?
- Yes: fixed in 11.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105050 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105050?
- 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.
How to fix
- Fixed in: 11.3.0
Technical details
PeaZip before 11.3.0 fails to properly sanitize quotation characters in archive filenames when constructing shell commands, leading to OS command injection. The vulnerability occurs in a non-default configuration where filename processing mishandles already-used quotation marks. An attacker can exploit this by creating a malicious archive with crafted filenames that break out of intended command quotes and inject arbitrary commands.
Affected products
- PeaZip PeaZip before 11.3.0
Timeline
- 2026-10-02: disclosed
- 2026-09-03: patched