CVE-2024-9056: bentoml/bentoml · Unthrottled Resource Allocation
Affects bentoml/bentomlSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
1. Immediately monitor and restrict incoming HTTP requests with malformed multipart boundaries, especially those containing unusual trailing characters like dashes. 2. Implement rate limiting and resource throttling on multipart/form-data parsing components to prevent excessive resource consumption. 3. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious multipart boundary patterns. 4. Upgrade BentoML to a patched version once available; in the meantime, consider applying temporary patches or workarounds such as input validation filters. 5. Isolate BentoML serving infrastructure behind reverse proxies that can filter malformed HTTP requests. 6. Conduct regular stress testing and monitoring to detect abnormal resource usage patterns indicative of exploitation attempts. 7. Educate DevOps and security teams about this vulnerability to ensure rapid detection and response. 8. Engage with BentoML community or vendor for updates and official patches.
Description
BentoML version v1.3.4post1 is vulnerable to a Denial of Service (DoS) attack. The vulnerability can be exploited by appending characters, such as dashes (-), to the end of a multipart boundary in an HTTP request. This causes the server to continuously process each character, leading to excessive resource consumption and rendering the service unavailable. The issue is unauthenticated and does not require any user interaction, impacting all users of the service.