Products / bentoml
bentoml
16 records.
- BentoML Dockerfile command injection via docker.base_image (sister of pending GHSA-w2pm-x38x-jp44 / CVE-2026-33744 / CVE-2026-35043) A multi-line base image value in the build config injects extra Dockerfile instructions, which then run as RUN commands during the docker build step.
- Dockerfile command injection via envs[*].name in bentofile.yaml (sibling fix-bypass of CVE-2026-33744 and CVE-2026-35043)
- BentoML has Information Disclosure in `bentoml build` via symlink traversal in the build context
- BentoML: Command Injection in cloud deployment setup script
- BentoML: SSTI via Unsandboxed Jinja2 in Dockerfile Generation
- BentoML has Dockerfile Command Injection via system_packages in bentofile.yaml
- BentoML Vulnerable to Arbitrary File Write via Symlink Path Traversal in Tar Extraction
- BentoML has a Path Traversal via Bentofile Configuration A crafted bentofile can reference paths outside the build context, so building it copies arbitrary host files such as keys into the packaged bento.
- BentoML SSRF Vulnerability in File Upload Processing
- BentoML's runner server Vulnerable to Remote Code Execution (RCE) via Insecure Deserialization Crafted POST requests make the BentoML runner server unpickle attacker-supplied data, which runs arbitrary code on the server.
- BentoML Allows Remote Code Execution (RCE) via Insecure Deserialization Request payloads are unpickled without validation, so a crafted HTTP request executes arbitrary code on the server.
- BentoML Open Redirect vulnerability A crafted URL makes the BentoML server redirect visitors to an arbitrary external site.
- BentoML deserialization vulnerability Setting the args-number parameter above 1 on the BentoML runner server causes attacker-supplied data to be deserialised, executing arbitrary code.
- BentoML vulnerable to Uncontrolled Resource Consumption
- BentoML Denial of Service (DoS) via Multipart Boundary
- Insecure deserialization in BentoML