Vulnerability in BentoPDF (CVE-2026-102354)
Summary
Vulnerability in BentoPDF (CVE-2026-102354). Confidential information can be exposed externally. Mitigation: upgrade to 2.8.7 or later.
Original description
The description as published by the source.
BentoPDF is a privacy-focused PDF toolkit that runs in the browser. In versions through 2.8.6, cloudflare/cors-proxy-worker.js performs a DNS-over-HTTPS safety check in hostnameResolvesToPrivate(), as used by isValidCertificateUrl() and isValidTsaUrl(), separately from the outbound fetch(targetUrl, ...). In deployments where PROXY_SECRET validation is not enabled, a direct client that controls authoritative DNS can forge the Origin header, supply a certificate, OCSP, CRL, or TSA URL that passes the proxy's accepted path checks, return a public address during validation, and return a private or link-local address during the later fetch. The endpoint can return allowed response bodies to the attacker, but exploitation requires precise timing, redirects and IP-literal obfuscation are blocked, and network reachability limits the target. This vulnerability is fixed in 2.8.7.
Source: NIST National Vulnerability Database NVD
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-102354 has been found in BentoPDF.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade BentoPDF to 2.8.7 or later.
If unsure, ask your IT team or search "BentoPDF CVE-2026-102354" on the vendor's site.
CVE-2026-102354 (BentoPDF) — CWE-367 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.8.7 — 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-367) exists in BentoPDF.
Check the vendor advisory for the affected versions of BentoPDF.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 2.8.7.
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 'BentoPDF' . 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 'BentoPDF' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
BentoPDFを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade BentoPDF to 2.8.7ステージング環境で 2.8.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。