Advisory record · GHSA-3cv5-q585-h563

Gotenberg has arbitrary PDF read via stampExpression and watermarkExpression in merge, split, and convert routes

CVSS 5.3 MediumEPSS 0.0031 · 24th percentile

Published by the GitHub Advisory Database at 7 May 2026, 00:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/gotenberg/gotenberg/v8Go<=8.31.0No fixed version yet
Identifiers
GHSA-3cv5-q585-h563 · CVE-2026-42593 · GO-2026-5080
Weakness (CWE)
CWE-22 · CWE-73
Published
7 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Gotenberg versions up to and including 8.31.0 are affected. On the merge, split, LibreOffice convert, and Chromium URL, HTML, and Markdown convert routes, an anonymous caller who sends a stamp or watermark expression with the PDF source type, without attaching a file, can make the server read any PDF the Gotenberg process can access and return its pages in the output. The source also describes a file-existence check based on the response code. No fixed version is listed; the source recommends applying a guard that requires an uploaded file for these routes.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 24th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 14 May 2026, 16:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 15:07 UTC First seen by agentprime
  3. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.