BentoML up to 1.4.39 Outbound Connection Safeguard _internal/utils/uri.py make_safe_connect server-side request forgery

Summaryinfo

A vulnerability labeled as problematic has been found in BentoML up to 1.4.39. Impacted is the function make_safe_connect of the file _internal/utils/uri.py of the component Outbound Connection Safeguard. Such manipulation leads to server-side request forgery. This vulnerability is documented as CVE-2026-78205. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in BentoML up to 1.4.39. It has been rated as problematic. Affected by this issue is the function make_safe_connect of the file _internal/utils/uri.py of the component Outbound Connection Safeguard. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality. CVE summarizes:

BentoML's outbound connection safeguard (make_safe_connect in _internal/utils/uri.py) blocks private, loopback, and link-local IP addresses but fails to reject the RFC 6598 shared address space (100.64.0.0/10, CGNAT). In versions 1.4.19 through 1.4.39, an unauthenticated attacker can supply URLs pointing to that range via multipart file handling (MultipartSerde.ensure_file) or JSON request parsing (JSONSerde.parse_request), causing the server to make outbound requests to internal hosts on CGNAT networks (Server-Side Request Forgery). This is an incomplete fix for CVE-2025-54381.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-78205 since 08/24/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/24/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-64680). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• BentoML

Version

• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 1.4.6
• 1.4.7
• 1.4.8
• 1.4.9
• 1.4.10
• 1.4.11
• 1.4.12
• 1.4.13
• 1.4.14
• 1.4.15
• 1.4.16
• 1.4.17
• 1.4.18
• 1.4.19
• 1.4.20
• 1.4.21
• 1.4.22
• 1.4.23
• 1.4.24
• 1.4.25
• 1.4.26
• 1.4.27
• 1.4.28
• 1.4.29
• 1.4.30
• 1.4.31
• 1.4.32
• 1.4.33
• 1.4.34
• 1.4.35
• 1.4.36
• 1.4.37
• 1.4.38
• 1.4.39

Website

• Product: https://github.com/bentoml/BentoML/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion