← Back
CVE-2026-40280
high
CVSS 7.5
SSRF (Server-Side Request Forgery) in github.com/gotenberg/gotenberg/v8 (CVE-2026-40280)
Summary
SSRF in github.com/gotenberg/gotenberg/v8 (CVE-2026-40280). Confidential information can be exposed externally. Exploitable via ``downloadFrom``. Mitigation: upgrade to `8.31.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40280** has been found in github.com/gotenberg/gotenberg/v8.
Attackers can target a specific entry point like ``downloadFrom`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/gotenberg/gotenberg/v8 to **8.31.0** or later.
If unsure, ask your IT team or search "github.com/gotenberg/gotenberg/v8 CVE-2026-40280" on the vendor's site.
CVE-2026-40280 (github.com/gotenberg/gotenberg/v8) — CWE-918 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `downloadFrom` / `FilterDeadline`
Patched: `8.31.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.
❓ What is the problem
**SSRF** (CWE-918) exists in github.com/gotenberg/gotenberg/v8. Attackers reach the vulnerable code path via ``downloadFrom`` without authentication.
📍 Affected scope
github.com/gotenberg/gotenberg/v8 — . Attack surface: `downloadFrom` / `FilterDeadline`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **8.31.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/gotenberg/gotenberg/v8 to 8.31.0ステージング環境で 8.31.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/gotenberg/gotenberg/v8
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"8.31.0"}]}]
References
- advisory https://github.com/advisories/GHSA-jjwv-57xh-xr6r
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40280
- package https://github.com/gotenberg/gotenberg
- web https://github.com/gotenberg/gotenberg/commit/3f01ca18d3cc21375a1e2da4b5a3f261c8548e47
- web https://github.com/gotenberg/gotenberg/security/advisories/GHSA-5q7p-7jgv-ww56
- web https://github.com/gotenberg/gotenberg/releases/tag/v8.31.0
- web https://github.com/advisories/GHSA-5q7p-7jgv-ww56