CVE-2024-7983: open-webui/open-webui · Unthrottled Resource Allocation
Affects open-webui/open-webuiSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopen-webui/open-webuipkg:github/open-webui/open-webuiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-7983, organizations should implement the following specific measures: 1) Restrict access to the markdown conversion endpoint by enforcing authentication and authorization controls to prevent unauthenticated usage. 2) Introduce rate limiting and request throttling on the endpoint to limit the number of markdown conversion requests per user or IP address, preventing resource exhaustion. 3) Implement input validation and sanitization to detect and reject maliciously crafted markdown payloads that could cause excessive processing. 4) Deploy resource usage monitoring and alerting on servers running open-webui to detect abnormal CPU or memory consumption patterns indicative of exploitation attempts. 5) Consider isolating the markdown conversion process in a sandboxed environment or container with strict resource limits to contain potential DoS effects. 6) Stay updated with open-webui releases and apply patches promptly once available. 7) If feasible, replace or supplement open-webui with alternative markdown rendering solutions that incorporate resource management features. These targeted actions go beyond generic advice by focusing on access control, resource management, and proactive detection specific to this vulnerability.
Description
In version 0.3.8 of open-webui, an endpoint for converting markdown to HTML is exposed without authentication. A maliciously crafted markdown payload can cause the server to spend excessive time converting it, leading to a denial of service. The server becomes unresponsive to other requests until the conversion is complete.