Gotenberg: Server-Side Request Forgery (SSRF) in github.com/gotenberg/gotenberg/v8

published 2026-05-07 6 mo ago modified 2026-06-25 4 mo ago also GHSA-rm4c-xj6x-49mw , GO-2026-5627 , EUVD-2026-30309

cvss: 8.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits: 0; none known

Gotenberg is a Docker-powered stateless API for PDF files. Prior to 8.32.0, the LibreOffice conversion endpoint (/forms/libreoffice/convert) passes uploaded documents directly to LibreOffice without inspecting their content. LibreOffice then fetches any embedded external URLs on its own, completely bypassing the SSRF filters. This vulnerability is fixed in 8.32.0.

Patch / fix

fixed in 1 distros 1

thecodingmachine gotenberg 8.32.0

govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 5 mo ago (2026-05-14)

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/gotenberg/gotenberg/security/advisories/GHSA-rm4c-xj6x-49mw referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
GitHub	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/gotenberg/gotenberg/v8	<=8.31.0 all versions	no fix listed
go	github.com/gotenberg/gotenberg/v7	all versions	no fix listed

Affected products

gotenberg gotenberg

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

github.com /gotenberg/gotenberg/security/advisories/GHSA-rm4c-xj6x-49mw
exploit, web, vendor-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2026-42591
advisory
github.com /gotenberg/gotenberg
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary