Skip to content
Fencer Intel
critical 9.8

CVE-2025-27520 in the critical feed json

BentoML Allows Remote Code Execution (RCE) via Insecure Deserialization

published last yr. modified 13d ago also EUVD-2025-9752 , GHSA-33xw-247w-6hmc , PYSEC-2026-294

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
40.6%
EPSS 40.6% chance of exploitation in 30 days, percentile 98%
public exploits
1
Metasploit

Summary

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. 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. It exists an unsafe code segment in serde.py. This vulnerability is fixed in 1.4.3.

Patch / fix

  • pypi bentoml 1.4.3
  • bentoml bentoml 1.4.3

Is CVE-2025-27520 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/linux/http/bentoml_rce_cve_2025_27520)
  2. Published

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

40.62% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi bentoml
>=1.3.4, <1.4.3
1.4.3

Affected products

  • bentoml BentoML

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.