UTC

bentoml

16 published advisories; version 1.4.39 or later fixes all but 4 of them.

Registry
PyPI
Advisories
16
Latest fix
1.4.39
Exploited in the wild
None listed
Advisories with no fix yet

4 advisories have no fixed release in any version yet. What can be done meanwhile:

General guidance from ShieldPi, not a vendor fix

  • Unsafe deserialization. Do not let it load files, models or data from sources you do not trust, and keep its RPC and socket ports reachable only from localhost or hosts you trust.GHSA-9g44-gwvm-hc44

Check your projects

shieldpi agent-config checks agent and MCP packages from npm and PyPI, not bentoml. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.

osv-scanner scan source -r .

Or check a lockfile against ShieldMap in your browser.

Provenance

Source: github.com/bentoml/bentoml, named in the package metadata (not verified)

10 of the last 10 releases of bentoml were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.

  • 1.4.40
  • 1.4.39
  • 1.4.38
  • 1.4.37
  • 1.4.36
  • 1.4.35
  • 1.4.34
  • 1.4.33
  • 1.4.32
  • 1.4.31

Green: published with provenance. Grey: without.

OpenSSF Scorecard: 7.0 of 10 on 2022-08-15.

No dangerous CI workflows
10/10
CI tokens read-only by default
0/10
Build dependencies pinned
7/10
Branch protection
6/10
Changes reviewed before merge
10/10
Signed releases
0/10
Actively maintained
10/10
Security policy
10/10
Full Scorecard →

Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.

Advisories
AdvisorySeverityAffectedFixed inPublished
BentoML Dockerfile command injection via docker.base_image (sister of pending GHSA-w2pm-x38x-jp44 / CVE-2026-33744 / CVE-2026-35043)CVE-2026-44345High<= 1.4.381.4.392026-05-11
Dockerfile command injection via envs[*].name in bentofile.yaml (sibling fix-bypass of CVE-2026-33744 and CVE-2026-35043)CVE-2026-44346High<= 1.4.381.4.392026-05-11
BentoML has Information Disclosure in `bentoml build` via symlink traversal in the build contextCVE-2026-40610Medium<= 1.4.381.4.392026-05-07
BentoML: Command Injection in cloud deployment setup scriptCVE-2026-35043High<= 1.4.371.4.382026-04-03
BentoML: SSTI via Unsandboxed Jinja2 in Dockerfile GenerationCVE-2026-35044High<= 1.4.371.4.382026-04-03
BentoML has Dockerfile Command Injection via system_packages in bentofile.yamlCVE-2026-33744High<= 1.4.361.4.372026-03-26
BentoML Vulnerable to Arbitrary File Write via Symlink Path Traversal in Tar ExtractionCVE-2026-27905High< 1.4.361.4.362026-03-03
BentoML has a Path Traversal via Bentofile ConfigurationCVE-2026-24123High< 1.4.341.4.342026-01-26
BentoML SSRF Vulnerability in File Upload ProcessingCVE-2025-54381Critical>= 1.4.0, < 1.4.191.4.192025-07-29
BentoML's runner server Vulnerable to Remote Code Execution (RCE) via Insecure DeserializationCVE-2025-32375Critical>= 1.0.0a1, < 1.4.81.4.82025-04-09
BentoML Allows Remote Code Execution (RCE) via Insecure DeserializationCVE-2025-27520Critical>= 1.3.4, < 1.4.31.4.32025-04-04
BentoML Open Redirect vulnerabilityGHSA-564p-rx2q-4c8vMedium<= 1.3.9No fix yet2025-03-20
BentoML deserialization vulnerabilityCVE-2024-9070Critical<= 1.4.5No fix yet2025-03-20
BentoML vulnerable to Uncontrolled Resource ConsumptionGHSA-hh3j-9m59-p8vcHigh<= 1.3.9No fix yet2025-03-20
BentoML Denial of Service (DoS) via Multipart BoundaryCVE-2024-9056High<= 1.4.5No fix yet2025-03-20
Insecure deserialization in BentoMLCVE-2024-2912Critical< 1.2.51.2.52024-04-16

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].