# CVE-2026-55229: Gotenberg: SSRF via LibreOffice document processing

> Attacker can trigger blind SSRF and limited local file disclosure via crafted documents in Gotenberg's LibreOffice conversion endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-2mrg-35hw-x3x9, GO-2026-5060

## What is CVE-2026-55229?

CVE-2026-55229 is a high-severity server-side request forgery vulnerability in gotenberg, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gotenberg is a Docker-powered stateless API for PDF files. Prior to 8.34.0, Gotenberg's /forms/libreoffice/convert endpoint allows a specially crafted document to cause LibreOffice to automatically retrieve external HTTP(S) resources and local file resources during document conversion, enabling blind SSRF and limited local file disclosure via linked image resource loading. This issue is fixed in version 8.34.0.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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.34.0 |
| `github.com/gotenberg/gotenberg/v8` | Go | All versions | 8.34.0 |
| `github.com/gotenberg/gotenberg/v8` | Go | All versions | 8.34.0 |
| `github.com/gotenberg/gotenberg/v7` | Go | All versions | None |

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

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

## Is CVE-2026-55229 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55229 exists.

Public exploit code:

- Gotenberg < 8.34.0 - Local File Disclosure (nuclei): http/cves/2026/CVE-2026-55229.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55229 is a high-severity server-side request forgery vulnerability in gotenberg, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55229 exists.

Affected packages and fixed versions:
- github.com/gotenberg/gotenberg/v8 (Go): affected all versions; fixed in 8.34.0
- github.com/gotenberg/gotenberg/v8 (Go): affected all versions; fixed in 8.34.0
- github.com/gotenberg/gotenberg/v8 (Go): affected all versions; fixed in 8.34.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-55229/ (Markdown: https://insights.sbomify.com/CVE-2026-55229/index.md)
```

## Sources

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

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