CVE-2026-42590
HighSummary
Gotenberg is a PDF file API that prior to version 8.30.0 had a vulnerability allowing the bypass of ExifTool's metadata write blocklist. Using ExifTool's group-prefix syntax, an attacker could rename, move, and create hard and soft links on the server.
Risk Assessment
This vulnerability could lead to unauthorized modification of files on the server, posing a serious threat to data integrity and system security.
Recommendation
It is recommended to update Gotenberg to version 8.30.0 or later to eliminate this vulnerability and minimize the risk of unauthorized file access.
Other vulnerabilities in Gotenberg
See all- CVE-2026-45742High
Gotenberg from version 8.10.0 until 8.33.0 has a race condition in the newContext function in pkg/modules/api/context.go, where multiple goroutines concurrently write to shared maps and slices. A crafted multipart request with many downloadFrom entries can trigger a fatal 'concurrent map writes' runtime error and terminate the process. The default configuration allows unauthenticated remote attacks, leading to denial of service. This issue is fixed in version 8.33.0.
- CVE-2026-42595High
Gotenberg is a PDF file API that prior to version 8.32.0 lacked default protection against HTTP/HTTPS-based SSRF attacks. An attacker could point Chromium at any internal IP and receive a response rendered as a PDF.
- CVE-2026-40893High
Gotenberg is a stateless API for PDF files that prior to version 8.31.0 did not properly check tags, allowing remote attackers to move, rename, and change permissions for arbitrary files.
- CVE-2026-45741High
Gotenberg in version 8.32.0 and earlier has a vulnerability in the IsPublicIP function that does not reject IPv6 prefixes such as 2002::/16, 64:ff9b::/96, fec0::/10, and others that can embed or route to non-public IPv4 destinations. A crafted DNS AAAA record can cause the outbound HTTP client to treat an address wrapping an internal destination (e.g., 169.254.169.254) as public, allowing access to cloud metadata services. This issue is fixed in version 8.33.0.
- CVE-2026-44829High
Gotenberg in version 8.32.0 and earlier has a vulnerability in filename handling where filepath.Base on Linux does not treat backslashes as path separators, so a multipart filename containing Windows-style parent directory components survives sanitization. A remote attacker can submit such a name, and when the resulting archive is extracted on a Windows system, files can be written outside the intended directory. This issue is fixed in version 8.33.0.
- CVE-2026-55229High
A vulnerability in Gotenberg prior to version 8.34.0 allows blind SSRF and limited local file disclosure via a specially crafted document sent to the /forms/libreoffice/convert endpoint. LibreOffice automatically retrieves external HTTP(S) resources and local files during document conversion.
- CVE-2026-39383High
Gotenberg version 8.29.1 has a blind SSRF vulnerability. An unauthenticated attacker with network access can force the server to make outbound HTTP POST requests to arbitrary internal or external destinations by supplying a crafted URL in the Gotenberg-Webhook-Url header.
- CVE-2026-40280High
Gotenberg versions 8.30.1 and earlier use the regular expression ^https?:// to check URLs in private IP deny-lists. Since Go normalizes the URL scheme to lowercase before establishing a connection, an attacker can bypass the block by using uppercase letters in the scheme (e.g., HTTP://). This allows unauthenticated requests to internal network services, including cloud metadata endpoints.
- CVE-2024-21527High
SSRF vulnerability in Gotenberg before version 8.1.0 allows local file inclusion via the /convert/html endpoint. An attacker can use an iframe pointing to localhost, e.g., <iframe src="\\localhost/etc/passwd">, leading to reading sensitive system files.
Original NVD description (English source)
Gotenberg is a Docker-powered stateless API for PDF files. Prior to 8.30.0, The ExifTool metadata write blocklist in Gotenberg can be bypassed using ExifTool's group-prefix syntax, enabling arbitrary file rename, move, hardlink, and symlink creation on the server. ExifTool supports group-prefix syntax where File:FileName is processed identically to FileName -- the prefix is stripped by SetNewValue in Writer.pl before tag matching. The safeKeyPattern regex (^[a-zA-Z0-9\-_.:]+$) allows colons, so prefixed tag names pass validation. Any prefix works: File:FileName, System:Directory, a:HardLink, etc. Additionally, FilePermissions, FileUserID, and FileGroupID pseudo-tags are not blocked at all and can modify file attributes without any prefix. This vulnerability is fixed in 8.30.0.

