← Back
CVE-2025-54381
SSRF (Server-Side Request Forgery) in bentoml (CVE-2025-54381)
Summary
SSRF in bentoml (CVE-2025-54381). Confidential information can be exposed externally. Exploitable via ``pathlib.Path``. Mitigation: upgrade to `1.4.19` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-54381** has been found in bentoml.
Attackers can target a specific entry point like ``pathlib.Path`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade bentoml to **1.4.19** or later.
If unsure, ask your IT team or search "bentoml CVE-2025-54381" on the vendor's site.
CVE-2025-54381 (bentoml) — CWE-918 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `pathlib.Path` / `PIL.Image.Image` / `JSONSerde` / `MultipartSerde`
Patched: `1.4.19` — 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 bentoml. Attackers reach the vulnerable code path via ``pathlib.Path`` without authentication.
📍 Affected scope
bentoml — . Attack surface: `pathlib.Path` / `PIL.Image.Image` / `JSONSerde` / `MultipartSerde`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.4.19**.
🛡️ 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 'bentoml' .` 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 'bentoml' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `bentoml` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade bentoml to 1.4.19ステージング環境で 1.4.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
bentoml
[{"type":"ECOSYSTEM","events":[{"introduced":"1.4.0"},{"fixed":"1.4.19"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-54381
- advisory https://github.com/advisories/GHSA-mrmq-3q62-6cc8
- package https://github.com/bentoml/BentoML
- package https://pypi.org/project/bentoml
- web https://github.com/bentoml/BentoML/security/advisories/GHSA-mrmq-3q62-6cc8
- web https://github.com/bentoml/BentoML/commit/534c3584621da4ab954bdc3d814cc66b95ae5fb8