# CVE-2026-126799: Gotenberg 8.31.0 before 8.38.0 SSRF via IPv6 Zone Identifiers in IsPublicIP

> Unauthenticated attackers can bypass Gotenberg's private IP deny-list using IPv6 zone identifiers to reach internal services and read responses.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-fqg9-x2xw-5crx, GHSA-wm5v-62gw-298q

## What is CVE-2026-126799?

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

### Official description

Gotenberg 8.31.0 before 8.38.0 contains a server-side request forgery vulnerability in IsPublicIP() that allows unauthenticated attackers to bypass private-IP deny-list protections using IPv6 zone identifiers. Attackers can append a zone such as %25eth0 to the unspecified address or blocked IPv6 prefixes in downloadFrom, webhook, or Chromium/LibreOffice URLs to reach internal services and read responses in the returned PDF.

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

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-126799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126799 is a medium-severity server-side request forgery vulnerability in gotenberg, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126799 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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