high CVSS 7.8

CVE-2026-35043·Python vulnerability

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Prior to 1.4.38, the cloud deployment path in src/bentoml/_internal/cloud/deployment.py was not included in the fix for CVE-2026-33744. Line 1648 interpolates system_packages directly into a shell command using an f-string without any quoting. The generated script is uploaded to BentoCloud as setup.sh and executed on the cloud build infrastructure during deployment, making this a remote code execution on the CI/CD tier. This vulnerability is fixed in 1.4.38.

Severity: high
Software: Python
Fixed in: 1.4.38
Published: 2026-04-06

Affected versions

Until: 1.4.38

Fixed in: 1.4.38

How to fix this CVE

Upgrade BentoML to version 1.4.38 or later to patch a critical shell command injection vulnerability in the cloud deployment module. This vulnerability allows arbitrary code execution during CI/CD pipeline execution when deploying models to BentoCloud. Organizations using BentoML for cloud deployments should prioritize this update immediately.

sudo dnf update python3-bentoml

Defensia detects this vulnerability

How to check if you are affected

Step 1: Check installed BentoML version by running: python3 -c "import bentoml; print(bentoml.__version__)"
Step 2: Verify if BentoML cloud deployment features are in use by checking for bentoml.cloud imports or bento.yaml cloud configuration in your project
Step 3: Search deployment logs in BentoCloud for suspicious shell command patterns or unexpected package installations in setup.sh execution logs
Step 4: Confirm the fix by upgrading to version 1.4.38+ and re-running: python3 -c "import bentoml; print(bentoml.__version__)" to verify the new version is active

FAQ

What is CVE-2026-35043?

CVE-2026-35043 is a shell command injection vulnerability in BentoML's cloud deployment module where system package names are interpolated directly into shell commands without proper escaping, allowing arbitrary code execution during model deployment to BentoCloud.

Is CVE-2026-35043 being actively exploited?

There is no evidence of active exploitation in the wild, and no public exploits are currently available. However, the attack surface is limited to organizations actively deploying models via BentoCloud.

What versions of BentoML are affected by CVE-2026-35043?

All versions of BentoML prior to 1.4.38 are affected. The vulnerability exists in the cloud deployment path (src/bentoml/_internal/cloud/deployment.py) and requires an upgrade to 1.4.38 or later.

How do I check if my server is vulnerable to CVE-2026-35043?

Run: python3 -c "import bentoml; print(bentoml.__version__)" and compare the version against 1.4.38. If your version is lower than 1.4.38 and you use BentoML cloud deployments, you are vulnerable.

Does Defensia detect CVE-2026-35043?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If BentoML is installed on a monitored server, CVE-2026-35043 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.

CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.

CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.

CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.

CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-35043. Free for 1 server.

Get started free