Patch & vulnerability status
PeaZip 11.2.0
Latest tracked version 11.2.0. Release status, tracked CVEs, and automated cross-platform patching for PeaZip.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Linux | 11.2.0 | 0 | 2026-08-10 |
| Mac | 11.2.0 | 0 | 2026-08-10 |
| Windows | 11.2.0 | 2 | 2026-08-10 |
Known vulnerabilities (CVEs) in PeaZip
Lavawall tracks 2 published CVEs affecting PeaZip, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2025-33026 | 2025-04-15 18:15:53 | MEDIUM (6) | In PeaZip through 10.4.0, there is a Mark-of-the-Web Bypass Vulnerability. This vulnerability allows attackers to bypass the Mark-of-the-Web protection mechanism on affected installations of PeaZip. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of archived files. When extracting files from a crafted archive that bears the Mark-of-the-Web, PeaZip does not propagate the Mark-of-the-Web to the extracted files. An attacker can leverage this vulnerability to execute arbitrary code in the context of the current user. NOTE: this is disputed because Mark-of-the-Web propagation can increase risk via security-warning habituation, and because the intended control sphere for file-origin metadata (e.g., HostUrl in Zone.Identifier) may be narrower than that for reading the file's content. | NETWORK |
| CVE-2023-6891 | 2023-12-17 04:15:07 | MEDIUM (8) | A vulnerability has been found in PeaZip 9.4.0 and classified as problematic. Affected by this vulnerability is an unknown functionality in the library dragdropfilesdll.dll of the component Library Handler. The manipulation leads to uncontrolled search path. An attack has to be approached locally. Upgrading to version 9.6.0 is able to address this issue. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-248251. NOTE: Vendor was contacted early, confirmed the existence of the flaw and immediately worked on a patched release. | LOCAL |
Why keeping PeaZip patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every PeaZip release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches PeaZip
Lavawall® watches PeaZip releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on PeaZip, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks PeaZip at version 11.2.0 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall continuously monitors PeaZip for newly disclosed CVEs and remediates them automatically as they appear.
Deploy the Lavawall® agent and PeaZip updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for PeaZip through public information and proprietary statistical analysis, and can patch it automatically across your fleet.