Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious archive to victim
-
DeliveryVictim opens archive in vulnerable PeaZip
-
ExploitCrafted filename breaks quoting in command string
-
ExecutionOS command injection executes
-
ImpactCode runs with user privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Leading special element handling
|
| Exploitation Conditions | Exploitation requires PeaZip running in an unspecified NON-DEFAULT configuration (the description explicitly scopes the flaw to such setups, so default installs are not affected), plus local user interaction: the victim must open or process an attacker-supplied archive. The attacker must craft a filename inside the archive that triggers the specific 'quotation character already used in the string' mishandling (reflected as AT:P in the CVSS 4.0 vector). Limiting factors: local attack vector (AV:L), required victim action (UI:A), dependence on a non-default setting, and the need to win the filename-quoting condition - together these substantially constrain real-world exploitability despite the high code-execution impact. Affected versions: all PeaZip releases before 11.3.0. |
| Impact | This is a moderate-priority issue that should be patched but does not warrant emergency response. The authoritative CVSS 4.0 vector (7.1) is internally consistent with the description: AV:L and UI:A mean the victim must locally open or interact with a malicious archive, and AT:P reflects the specific precondition that a filename contain a quotation character that is mishandled - this is not drive-by remote exploitation. The description's explicit 'non-default configuration' qualifier is a significant risk reducer that the CVSS vector only partially captures (via AT:P), meaning the vulnerable code path is not reachable in stock PeaZip installs. No EPSS score, KEV listing, SSVC decision, or POC was provided in the intelligence, so exploitation probability signals are absent rather than low - do not read the missing EPSS as 'safe.' The high VC/VI/VA (command injection yielding code execution) means technical impact is severe IF the preconditions are met, but the combination of local vector, required user interaction, non-default config, and a filename-crafting requirement makes mass or automated exploitation unlikely. Net: genuine but conditional risk, best characterized as targeted/social-engineering-dependent rather than wormable. |
| Exploit ScenarioDerived | An attacker crafts an archive containing a file whose name embeds OS command syntax exploiting the mishandled 'quotation character already used in the string' condition, then delivers it to a victim running PeaZip in the specific non-default configuration. When the victim opens or processes the archive, the malformed filename is passed to a shell and the attacker's commands execute with the victim's privileges. No public exploit code was identified in the provided intelligence, so this scenario is inferred from the description and CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
OS command injection in PeaZip before 11.3.0 allows an attacker to run arbitrary commands on a victim's machine by embedding a specially crafted filename in an archive, provided PeaZip is running in a specific non-default configuration. The root cause is mishandling of the 'quotation character already used in the string' condition, which lets the injected filename escape the application's quoting and reach the shell; the CVSS 4.0 vector records no required privileges (PR:N) but explicitly captures attack prerequisites (AT:P), and exploitation is local with user interaction, meaning the victim must open or process the malicious archive. No public exploit code has been identified and the issue is not listed in CISA KEV; the vendor has addressed it in PeaZip 11.3.0, and the independent assessment rates this moderate priority - worth patching, but not an emergency.
RemediationAI
Upgrade to PeaZip 11.3.0 or later, which is the vendor-released patch for this issue and is available from the official release page (https://github.com/peazip/PeaZip/releases/tag/11.3.0); the corrected source is published at https://github.com/peazip/PeaZip/tree/sources/peazip-sources for anyone building from source, with the specific fix in commit 009fc35530e26729863969eddf4c18f1b48331cf. If immediate upgrade is not possible, the most effective compensating control is to revert PeaZip to its default configuration, since the vulnerability is explicitly limited to a non-default setup and default installations are not affected - the trade-off is loss of whatever workflow feature that setting enabled. Additionally, do not open, extract, or test archives from untrusted sources, and run PeaZip under a low-privilege account or in a sandboxed/containerized environment so that any successful command injection is contained rather than executing with the user's full rights; these controls reduce likelihood and blast radius but do not eliminate the flaw, so patching remains the definitive fix. Because exploitation needs local access plus a victim opening a crafted archive (CVSS AV:L/UI:A/AT:P, with no public exploit code identified and no CISA KEV listing), the independent assessment treats this as a moderate-priority patch to schedule in normal maintenance rather than an emergency response.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PeaZip is a cross-platform file archiver and compression front-end that wraps backends such as 7z/p7zip and Pea and shells out to external tools for many archive operations. When extracting, testing, or otherwise handling an archive, member filenames originate in attacker-controllable archive metadata and are passed into command strings, so any weakness in how those names are escaped becomes a command-injection primitive. CVE-2026-105050 is classified as CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize), a root-cause class in which input is validated or escaped before it is canonicalized, so the validation operates on a different representation of the string than the one that ultimately reaches the sink. Here the concrete manifestation is that a filename containing the same quotation character already used in the surrounding string is mishandled, and the quoting protection fails, allowing shell metacharacters in the filename to be interpreted as commands (the CWE-78 command-injection outcome reflected by the 'Command Injection' tag). The condition only manifests in a non-default PeaZip configuration, which means the vulnerable command-construction path is not exercised by a stock installation. The CPE entry cpe:2.3:a:peazip:peazip:*:*:*:*:*:*:*:* denotes that all PeaZip builds before the 11.3.0 release are in scope, which aligns with the vendor's release notes stating that the 11.3.0 update is recommended 'due to multiple security fixes and improvements' and that its bundled backends were refreshed to 7z/p7zip 26.03 and Pea 1.33.
Know when Peazip gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Local archive must be opened by the victim (AV:L/UI:R); the non-default config plus quotation-mishandling precondition map to AC:H; no prior auth needed (PR:N); command injection yields full C/I/A impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Executive ViewAI
PeaZip releases prior to 11.3.0 contain a command-injection flaw that a crafted archive filename can trigger to run arbitrary code on the machine of a user who extracts it while PeaZip is running in a non-default configuration. Because exploitation requires the victim to open the malicious archive, the exposure is confined to individual endpoints rather than shared servers, but any resulting code executes with that user's privileges and could serve as a foothold for further access. Leadership should treat this as a routine, time-bound third-party patch activity rather than an active incident.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
An issue in Giorgio Tani peazip v.9.0.0 allows attackers to cause a denial of service via the End of Archive tag functio
Path traversal in PeaZip's archive object preview handler allows a crafted archive entry to escape the extraction direct
Out-of-bounds write in PeaZip's PEA archive extractor allows an attacker to execute arbitrary code with the privileges o
A vulnerability has been found in PeaZip 9.4.0 and classified as problematic. Rated high severity (CVSS 7.8), this vulne
In PeaZip through 10.4.0, there is a Mark-of-the-Web Bypass Vulnerability. Rated medium severity (CVSS 6.1), this vulner
PeaZip 10.5.0 through 11.2.0 on Windows fails to show its 'Do you want to run this file?' confirmation before launching
EUVD-2026-91838
GHSA-377g-778f-272q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB