medium CVSS 5.5

CVE-2026-40610·Python vulnerability

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. In versions 1.4.38 and prior, the build packaging workflow follows attacker-controlled symlinks inside the build context and copies the referenced file contents into the generated Bento artifact. If a victim builds an untrusted repository or other attacker-supplied build context, the attacker can place a symlink such as loot.txt -> /tmp/outside-marker.txt or a link to a more sensitive local file. When bentoml build runs, BentoML dereferences the symlink and packages the target file contents into the Bento. The leaked file can then propagate further through export, push, or containerization workflows. An attacker can exfiltrate local files from the build host into the Bento artifact, exposing secrets such as cloud credentials, SSH keys, API tokens, environment files, or other sensitive local configurations. Because Bento artifacts are commonly exported, uploaded, stored, or containerized after build, the leaked file contents can spread beyond the original build machine. This issue has been fixed in version 1.4.39.

Severity
medium
Software
Python
Fixed in
1.4.39
Published
2026-05-22

Affected versions

Until: 1.4.39

Fixed in: 1.4.39

How to fix this CVE

Update BentoML to version 1.4.39 or later to patch the symlink-following vulnerability in the build packaging workflow. If you are using BentoML for model serving, immediately audit any Bento artifacts built from untrusted sources or external repositories, as they may contain exfiltrated sensitive files such as credentials or SSH keys. Review your build environment logs to identify any suspicious symlink creation or file access patterns during recent build operations.

sudo dnf upgrade python3-bentoml

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed BentoML version by running `pip show bentoml | grep Version`
  2. Step 2: Verify if the version is 1.4.38 or earlier; if so, the system is vulnerable
  3. Step 3: Search build logs for symlink creation events using `find /path/to/build/context -type l -ls` to identify any suspicious symbolic links
  4. Step 4: Confirm the fix by upgrading BentoML and re-running `pip show bentoml` to verify version 1.4.39 or later is installed

FAQ

What is CVE-2026-40610?

CVE-2026-40610 is a local file disclosure vulnerability in BentoML versions up to 1.4.38 where the build workflow unsafely dereferences symlinks within the build context, allowing attackers to inject symbolic links that cause sensitive local files (credentials, SSH keys, API tokens) to be packaged into Bento artifacts.

Is CVE-2026-40610 being actively exploited?

No, CVE-2026-40610 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are currently available. However, the attack requires only local access to the build context, making it a plausible threat in shared development environments.

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

BentoML versions 1.4.38 and all prior versions are vulnerable. Version 1.4.39 and later include the fix.

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

Run `pip show bentoml` and check the Version field. If the version is 1.4.38 or earlier, you are vulnerable. If version 1.4.39 or later is installed, you are patched.

Does Defensia detect CVE-2026-40610?

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

Related Python CVEs

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-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-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-40610. Free for 1 server.

Get started free