CVE-2026-104024 PeaZip CVE debrief

Who should care

Defenders and administrators responsible for PeaZip installations, especially in environments where archive files from untrusted sources are frequently opened, should prioritize verifying exposure of PeaZip installations to this vulnerability. They should review compensating controls for exposed systems while remediation is scheduled and verified, and track exceptions, retest remediated assets, and close the item only after evidence is documented.

Why it matters

Defenders should prioritize verifying exposure of PeaZip installations to this vulnerability, especially in environments where archive files from untrusted sources are frequently opened, as it allows execution of programs or commands without confirmation.

• Execution of arbitrary programs or commands without user confirmation
• Potential for lateral movement and exploitation in environments with shared archive files
• Need for verification of PeaZip version and exposure to crafted archive files

Technical summary

The dangerous-extension confirmation in PeaZip's archive object viewer is incomplete, allowing execution of programs or commands from crafted archive entries without confirmation. This vulnerability affects PeaZip versions 10.5.0 through 11.2.0 on Windows, enabling attackers to execute arbitrary programs or commands by convincing victims to open crafted archive entries. The vulnerability is caused by an exact string comparison of the entry extension against a hard-coded list of seven extensions (exe cmd msi bat ps1 vbs reg), which is incomplete and allows execution of programs or commands from crafted archive entries without confirmation.

Defensive priority

Defenders should prioritize verifying exposure of PeaZip installations to this vulnerability, especially in environments where archive files from untrusted sources are frequently opened.

Recommended defensive actions

• Verify PeaZip installations are updated to version 11.3.0 or later
• Restrict opening archive files from untrusted sources
• Monitor for suspicious archive file openings
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability in PeaZip versions 10.5.0 through 11.2.0 on Windows, where an incomplete list of disallowed inputs allows execution of a program or command from a crafted archive entry without confirmation. The dangerous-extension confirmation in PeaZip's archive object viewer is incomplete, allowing execution of programs or commands from crafted archive entries without confirmation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.