← Back
CVE-2026-40610
medium
CVSS 5.5
Vulnerability in bentoml (CVE-2026-40610)
Summary
vulnerability in bentoml (CVE-2026-40610). Confidential information can be exposed externally. Exploitable via ``src_file``. Mitigation: upgrade to `1.4.39` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40610** has been found in bentoml.
Attackers can target a specific entry point like ``src_file`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade bentoml to **1.4.39** or later.
If unsure, ask your IT team or search "bentoml CVE-2026-40610" on the vendor's site.
CVE-2026-40610 (bentoml) — CWE-59 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: `src_file` / `ctx_path` / `shutil.copy` / `loot.txt`
Patched: `1.4.39` — 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
**A vulnerability** (CWE-59) exists in bentoml. Attackers reach the vulnerable code path via ``src_file`` without authentication.
📍 Affected scope
bentoml — . Attack surface: `src_file` / `ctx_path` / `shutil.copy` / `loot.txt`.
🔥 Severity
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.4.39**.
🛡️ 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.39ステージング環境で 1.4.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
bentoml
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.39"}]}]
PyPI
bentoml
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.39"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40610
- package https://github.com/bentoml/BentoML
- web https://github.com/bentoml/BentoML/commit/5fb7cd41f92e2a56b45391284cf15b9ac9963a1f
- web https://github.com/bentoml/BentoML/releases/tag/v1.4.39
- web https://github.com/bentoml/BentoML/security/advisories/GHSA-mcfx-4vc6-qgxv
- web https://github.com/advisories/GHSA-mcfx-4vc6-qgxv