Advisory record · GHSA-mrmq-3q62-6cc8

BentoML SSRF Vulnerability in File Upload Processing

CVSS 9.9 CriticalCriticalEPSS 0.14 · 96th percentile

Critical, because:

  • CVSS score 9.9: 9.0 or more.
  • CVSS score 9.9 (7.0 or more) and EPSS 0.14 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jul 2025, 19:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
bentomlPyPI>=1.4.0, <1.4.191.4.19
Identifiers
GHSA-mrmq-3q62-6cc8 · CVE-2025-54381 · PYSEC-2026-297
Weakness (CWE)
CWE-918
Published
29 Jul 2025
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

BentoML versions 1.4.0 before 1.4.19 (PyPI package bentoml) contain a server-side request forgery flaw in file upload handling, where URLs supplied in multipart form fields or JSON bodies are downloaded by the server without checking for internal network addresses. An unauthenticated remote attacker who can reach an endpoint with file-type parameters can make the server send arbitrary HTTP requests, which may expose internal services or cloud metadata. The fix is to upgrade to bentoml 1.4.19.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.9 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.14, the 96th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.