Security readout for executives and security teams
Plain-English summary
CVE-2026-24123 affects BentoML before 1.4.34. A malicious project configuration can cause a build process to quietly copy sensitive local files into a Bento archive. Risk is highest for teams building AI services from third-party, forked, or externally supplied BentoML projects.
Executive priority
Treat as a high-priority supply-chain confidentiality issue for AI engineering teams. Prioritize build systems and developer workstations that process external BentoML projects or store credentials. Upgrade promptly and reduce secrets available during builds.
Technical view
BentoML bentofile.yaml path fields allowed path traversal before 1.4.34, including description, docker.setup_script, docker.dockerfile_template, and conda.environment_yml. If a victim builds a crafted bentofile, arbitrary filesystem files may be embedded into the resulting bento. The CVSS vector indicates network attackability with required user interaction and high confidentiality impact.
Likely exposure
Organizations using BentoML versions earlier than 1.4.34 are exposed when developers or CI systems build bentos from untrusted or insufficiently reviewed repositories. Systems holding SSH keys, cloud credentials, environment files, or deployment secrets on build hosts face the greatest confidentiality risk.
Exploitation context
The sources do not report active exploitation, and this CVE is not marked KEV. Exploitation requires a victim to build a malicious bentofile. The main scenario is supply-chain abuse where secrets are embedded into artifacts and later exposed through registries, deployment, or sharing.
Researcher notes
The advisory identifies CWE-22 path traversal in multiple bentofile.yaml fields and states the issue is patched in 1.4.34. Available sources describe confidentiality impact, not integrity or availability impact. No public source in the bundle confirms exploitation in the wild.
Mitigation direction
- Upgrade BentoML to version 1.4.34 or later.
- Do not build untrusted BentoML projects on hosts containing sensitive files.
- Review externally supplied bentofile.yaml files before building.
- Use isolated build environments with minimal secrets and credentials.
- If exposure is suspected, inspect produced bentos and rotate affected secrets.
Validation and detection
- Inventory BentoML installations and identify versions earlier than 1.4.34.
- Review CI pipelines that build bentos from forks or external repositories.
- Audit bentofile.yaml path fields for unsafe external file references.
- Check whether built bento archives contain unexpected sensitive files.
- Confirm the 1.4.34 fix is deployed where BentoML builds occur.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24123 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N2.84Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/bentoml/BentoML/security/advisories/GHSA-6r62-w2q3-48hfCVE reference · x_refsource_CONFIRM
- https://github.com/bentoml/BentoML/commit/84d08cfeb40c5f2ce71b3d3444bbaa0fb16b5ca4CVE reference · x_refsource_MISC
- https://github.com/bentoml/BentoML/releases/tag/v1.4.34CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.