Vulnerability in github.com/gotenberg/gotenberg/v8 (CVE-2026-42597)
Summary
Vulnerability in github.com/gotenberg/gotenberg/v8 (CVE-2026-42597). Confidential information can be exposed externally. Exploitable via AllowedFilePrefixes. Mitigation: upgrade to 8.32.0 or later.
Original description
The description as published by the source.
Gotenberg is a Docker-powered stateless API for PDF files. Prior to 8.32.0, the /forms/chromium/convert/url and /forms/chromium/screenshot/url routes accept url=file:///tmp/... from anonymous callers. The default Chromium deny-list intentionally exempts file:///tmp/ so HTML/Markdown routes can load their own request-local assets, and those routes apply a per-request AllowedFilePrefixes guard to scope the read. The URL routes never set AllowedFilePrefixes, so the scope guard silently skips. Alice enumerates /tmp/, walks Gotenberg's per-request working directories, and reads the raw source files of other in-flight conversions as rendered PDF output. This vulnerability is fixed in 8.32.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42597 has been found in github.com/gotenberg/gotenberg/v8.
Attackers can target a specific entry point like AllowedFilePrefixes over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade github.com/gotenberg/gotenberg/v8 to 8.32.0 or later.
If unsure, ask your IT team or search "github.com/gotenberg/gotenberg/v8 CVE-2026-42597" on the vendor's site.
CVE-2026-42597 (github.com/gotenberg/gotenberg/v8) — CWE-73 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: AllowedFilePrefixes / FilterOutboundURL / Fetch.requestPaused / convertUrlRoute
Patched: 8.32.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) exists in github.com/gotenberg/gotenberg/v8. Attackers reach the vulnerable code path via AllowedFilePrefixes without authentication.
Check the vendor advisory for the affected versions of github.com/gotenberg/gotenberg/v8. Attack surface: AllowedFilePrefixes / FilterOutboundURL / Fetch.requestPaused / convertUrlRoute.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 8.32.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/gotenberg/gotenberg/v8' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/gotenberg/gotenberg/v8' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gotenberg/gotenberg/v8を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/gotenberg/gotenberg/v8 to 8.32.0ステージング環境で 8.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com