# CVE-2026-44829: Gotenberg: Path traversal in zip entry name via Windows-style separators in upload filename

> Remote attackers can write arbitrary files on downstream Windows systems via path traversal in zip entry names when extracting archives generated by Gotenberg.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L`)
- **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:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-hwc4-gmrw-5222, GO-2026-5443

## What is CVE-2026-44829?

CVE-2026-44829 is a high-severity path traversal vulnerability in gotenberg, published on 19 Aug 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

Gotenberg is a Docker-powered stateless API for PDF files. In 8.32.0 and earlier, filename handling in pkg/modules/api/context.go uses filepath.Base on Linux, which does not treat backslashes as path separators, so a multipart filename containing Windows-style parent directory components survives sanitization. The original filename flows through ctx.diskToOriginal and the multi-output PDF routes into archives.FilesFromDisk and archives.Zip.Archive as the generated zip entry name. A remote attacker can submit a name such as ........\Windows\System32\evil.pdf through an upload or an upstream downloadFrom Content-Disposition header, and a Windows archive extractor can write the resulting file outside the intended extraction directory. The affected paths include /forms/pdfengines/split and other multi-output PDF, LibreOffice, and conversion routes, and exploitation can cause arbitrary file writes on a downstream Windows system when a user or process extracts the returned archive. This issue is fixed in version 8.33.0.

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

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

4 open source packages ship an affected version, including github.com/gotenberg/gotenberg/v8 and github.com/gotenberg/gotenberg/v7.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gotenberg/gotenberg/v8` | Go | All versions | 8.33.0 |
| `github.com/gotenberg/gotenberg/v8` | Go | All versions | 8.33.0 |
| `github.com/gotenberg/gotenberg/v8` | Go | All versions | 8.33.0 |
| `github.com/gotenberg/gotenberg/v7` | Go | All versions | None |

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

Upgrade github.com/gotenberg/gotenberg/v8 to 8.33.0 or later.

## Is CVE-2026-44829 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44829 is a high-severity path traversal vulnerability in gotenberg, published on 19 Aug 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-44829 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gotenberg/gotenberg/v8 (Go): affected all versions; fixed in 8.33.0
- github.com/gotenberg/gotenberg/v8 (Go): affected all versions; fixed in 8.33.0
- github.com/gotenberg/gotenberg/v8 (Go): affected all versions; fixed in 8.33.0
- github.com/gotenberg/gotenberg/v7 (Go): affected all versions; no fix listed

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-44829/ (Markdown: https://insights.sbomify.com/CVE-2026-44829/index.md)
```

## Sources

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

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