# CVE-2026-104024: Security feature bypass in PeaZip

> Attackers can execute arbitrary commands via crafted archive entries by bypassing PeaZip's incomplete dangerous-extension confirmation list.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7pj5-7mcm-w2c6

## What is CVE-2026-104024?

CVE-2026-104024 is a medium-severity vulnerability in PeaZip, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Incomplete List of Disallowed Inputs (CWE-184) in the dangerous-extension confirmation of the archive object viewer (peach.pas, grid_obj_open) in PeaZip 10.5.0 through 11.2.0 on Windows allows an attacker who convinces a victim to open an entry of a crafted archive to execute a program, or an arbitrary command, with no confirmation dialog. The prompt (Do you want to run this file?) is gated by SECEXTCONST, a hard-coded list of seven extensions (exe cmd msi bat ps1 vbs reg); the check is an exact string comparison of the entry extension against that list, so it answers only whether the extension is one of the seven and never whether the shell will execute the file. Shell-executable and scripting-host types that Windows runs through ShellExecuteW are absent from the list, among them .url and .lnk. An archived Windows Internet Shortcut (.url) whose URL line is attacker-controlled is launched with no prompt, while the byte-identical content in an entry named .bat does raise the warning in the same session. A .lnk entry raises the ceiling from launching a program to running a command line, because a Windows shortcut carries arguments: a proof-of-concept shortcut targeting cmd.exe with an attacker-chosen command line executed with no prompt. The shortcut target is not confined to the local disk; the shell also resolved an attacker-named UNC path (fetching a remote payload was only attempted, not demonstrated). No privilege escalation; everything runs as the user who opened the archive.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-104024?


## How do I fix CVE-2026-104024?

No fix has been published for CVE-2026-104024 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104024 being exploited?

There is no known exploitation of CVE-2026-104024 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104024 and fix it if it is affected.

What it is: CVE-2026-104024 is a medium-severity vulnerability in PeaZip, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104024 in the wild and no public exploit code.

Affected product: PeaZip. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104024/ (Markdown: https://insights.sbomify.com/CVE-2026-104024/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104024
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104024
- OSV: https://osv.dev/vulnerability/CVE-2026-104024

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104024/
Summaries are generated and may contain mistakes; the official description above is the record.