CVE-2026-24123

GHSA-6r62-w2q3-48hf MEDIUM
Published January 26, 2026
CISO Take

If your team builds BentoML packages from external or community-sourced bentofiles, upgrade to 1.4.34 immediately — a malicious bentofile.yaml can silently exfiltrate SSH keys, .env files, and credentials into your bento archive before it reaches a registry. The real risk is supply chain: a compromised open-source model repo can trigger credential theft during a routine CI/CD build. Patch first, then audit any bento archives built from untrusted sources for unexpected file inclusions.

Affected Systems

Package Ecosystem Vulnerable Range Patched
bentoml pip < 1.4.34 1.4.34
bentoml pip No patch

Severity & Risk

CVSS 3.1
6.5 / 10
EPSS
0.0%
chance of exploitation in 30 days
KEV Status
Not in KEV
Sophistication
Trivial

Recommended Action

  1. 1. Patch: Upgrade BentoML to >= 1.4.34 immediately across all build environments. 2. Audit: Inspect bento archives built on affected versions for unexpected non-model files — scan for .ssh, .env, credentials, and config files outside expected directory structures. 3. Trust controls: Never run bentoml build on untrusted bentofiles without prior code review of all file path fields. 4. Detection: Add pre-build linting rules to validate bentofile.yaml path fields against strict allowlists, failing builds on path traversal patterns (e.g., ../). 5. CI/CD hygiene: Ensure build environments are ephemeral, isolated, and credentials are injected via secrets managers rather than stored as on-disk files accessible during builds. 6. Registry audit: Review push history for model registries that received artifacts built by BentoML < 1.4.34 and rotate any credentials that may have been co-located on build hosts.

Classification

Compliance Impact

This CVE is relevant to:

EU AI Act
Art.9 - Risk Management System Article 15 - Accuracy, robustness and cybersecurity Article 9 - Risk management system
ISO 42001
6.1.2 - AI risk assessment 8.4 - AI system security A.6.2 - AI System Lifecycle Processes A.9.4 - Supply Chain Management for AI Systems
NIST AI RMF
GOVERN 1.1 - Organizational Policies for AI Risk GOVERN 6.1 - Policies for AI risk and trustworthiness MANAGE 2.2 - Mechanisms for tracking identified AI risks MANAGE 2.4 - Mechanisms for Tracking Identified AI Risks
OWASP LLM Top 10
LLM05 - Supply Chain Vulnerabilities LLM06 - Sensitive Information Disclosure

Technical Details

NVD Description

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Prior to version 1.4.34, BentoML's `bentofile.yaml` configuration allows path traversal attacks through multiple file path fields (`description`, `docker.setup_script`, `docker.dockerfile_template`, `conda.environment_yml`). An attacker can craft a malicious bentofile that, when built by a victim, exfiltrates arbitrary files from the filesystem into the bento archive. This enables supply chain attacks where sensitive files (SSH keys, credentials, environment variables) are silently embedded in bentos and exposed when pushed to registries or deployed. Version 1.4.34 contains a patch for the issue.

Exploitation Scenario

An adversary publishes a popular open-source ML project on GitHub with a crafted bentofile.yaml where the docker.setup_script field contains a path traversal payload pointing to ../../../../home/user/.ssh/id_rsa or a cloud credentials file. A developer or CI/CD pipeline clones the repo and runs bentoml build to package the model for deployment — standard MLOps workflow. BentoML follows the traversal path and silently embeds the SSH private key inside the bento archive without any warning. The team pushes the archive to a shared or public model registry. The adversary pulls the archive and extracts the embedded credential, enabling lateral movement into production infrastructure or cloud environments.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Timeline

Published
January 26, 2026
Last Modified
February 3, 2026
First Seen
January 26, 2026