Gotenberg vulnerable to argument injection via newlines in ExifTool metadata values
What fixes it
- 8.31.0github.com/gotenberg/gotenberg/v8, GoOSV
go get github.com/gotenberg/gotenberg/v8@v8.31.0
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Timeline
- 6 May 2026, 20:46 UTCPublishedCVE List
- 27 Oct 2026, 18:54 UTCExploit code publicGitHub proof-of-concept repositories
Public exploit code and templates 1
- Scanner templateGotenberg <= 8.30.1 - Remote Code ExecutionNuclei
Listed so defenders can prioritize. Threatline links to the source and does not host exploit code.
Reports 1
1 outlet mention it. Reports are not confirmation; each links to its source.
Description
Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.
Text from CVE List
Affected versions 2
- gotenbergaffected: <= 8.30.1CVE List
- github.com/gotenberg/gotenberg/v8, Gofrom first release, fixed in 8.31.0OSV