dbcve.org
PeazipApplication

CVE-2025-33026

HIGH · 7.8 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to after 10.4.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PeaZip fails to propagate the Mark-of-the-Web (MOTW) security flag when extracting files from archives. When a user extracts files from an archive that carries the MOTW (Zone.Identifier), the extracted files lose this security marker, allowing potentially malicious executables to run without triggering Windows security warnings.

MitigationAvoid extracting files from untrusted or unverified archives; implement additional endpoint protection that scans extracted files before execution; await an official PeaZip update that implements MOTW propagation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PeazipApplication
Affected:<= 10.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if PeaZip is installed
    Search for PeaZip in standard installation locations or use system search to confirm presence on the system
    Affected if PeaZip executable is found on the system
  2. Determine installed PeaZip version
    Open PeaZip and go to Help > About, or right-click the PeaZip executable, select Properties, and check the Details tab for the version number
    Affected if Installed version is 10.4.0 or lower
  3. Compare version to affected range
    Match the discovered version number against the affected range: versions 10.4.0 and below
    Affected if Version is less than or equal to 10.4.0

Environment is affected if PeaZip version 10.4.0 or lower is installed, since the vulnerability allows MOTW to be stripped from extracted files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 10.4.0
Interim mitigation

Avoid extracting files from untrusted or unverified archives; implement additional endpoint protection that scans extracted files before execution; await an official PeaZip update that implements MOTW propagation.

Recommended fix High confidence

PeaZip version > 10.4.0 (latest stable release)

  1. 1. Visit the official PeaZip download page at peazip.github.io
  2. 2. Download the latest version of PeaZip (version higher than 10.4.0)
  3. 3. Uninstall the current vulnerable version of PeaZip
  4. 4. Install the newly downloaded version
  5. 5. Verify the installed version is newer than 10.4.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Peazip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33026 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33026 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data