Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

BentoML vulnerable to Uncontrolled Resource Consumption

GHSA-hh3j-9m59-p8vc

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI bentoml

    Affected
    <= 1.3.9
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

In bentoml/bentoml version 1.3.9, the /login endpoint of the newly integrated Gradio app is vulnerable to a Denial of Service (DoS) attack. This vulnerability can be exploited by appending characters, such as dashes (-), to the end of a multipart boundary in an HTTP request. The server continuously processes each character, leading to excessive resource consumption and rendering the service unavailable. The issue is unauthenticated and does not require any user interaction.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-hh3j-9m59-p8vc

  2. Revision 1 · created ·

    Published from osv record GHSA-hh3j-9m59-p8vc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-hh3j-9m59-p8vc

Advisory: BentoML vulnerable to Uncontrolled Resource Consumption
IDs: GHSA-hh3j-9m59-p8vc
Record: https://patchnext.com/advisories/ghsa-hh3j-9m59-p8vc (revision 2, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI bentoml: affected <= 1.3.9

## Suggested inspection (read-only)
- `python -m pip show bentoml`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on bentoml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hh3j-9m59-p8vc (OSV record GHSA-hh3j-9m59-p8vc lists affected ranges: PyPI bentoml >=0 <=1.3.9)
- Verified: https://github.com/advisories/GHSA-hh3j-9m59-p8vc (GitHub-reviewed advisory GHSA-hh3j-9m59-p8vc lists affected ranges: PyPI bentoml >=0 <=1.3.9)

Commands are suggestions: review each one before running it.

Loading voting…