BentoML Allows Remote Code Execution (RCE) via Insecure Deserialization
Published Apr 4, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
BentoML Allows Remote Code Execution (RCE) via Insecure Deserialization
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A Remote Code Execution (RCE) vulnerability caused by insecure deserialization has been identified in the latest version(v1.4.2) of BentoML. It allows any unauthenticated user to execute arbitrary code on the server.
Potential impact
Remote Code Execution (RCE).
Technical context
It exists an unsafe code segment in serde.py: Through data flow analysis, it is confirmed that the payload content is sourced from an HTTP request, which can be fully manipulated by the attack. Due to the lack of validation in the code, maliciously crafted serialized data can execute harmful actions during deserialization.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- IMMEDIATE
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Apr 4, 2025 · Last refreshed Nov 3, 2026