# CVE-2026-102332: Dozzle before 11.1.2 Path Traversal via Log ZIP Download

> Attackers can write files outside the extraction directory by exploiting path traversal in log ZIP downloads, requiring users to extract the logs.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-746p-gqhc-m84c

## What is CVE-2026-102332?

CVE-2026-102332 is a medium-severity path traversal vulnerability in amir20 dozzle, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Dozzle versions before 11.1.2 fail to sanitize container display names when building ZIP archive entry names in the log download endpoint. Attackers who can label containers can use path traversal sequences to write files outside the extraction directory when users download and extract logs.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-102332 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102332 is a medium-severity path traversal vulnerability in amir20 dozzle, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102332 in the wild and no public exploit code.

Affected product: amir20 dozzle. 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-102332/ (Markdown: https://insights.sbomify.com/CVE-2026-102332/index.md)
```

## Sources

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

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