CVE-2026-54283: Starlette · request.form() limits silently ignored for application/x-www-form-urlencoded enable DoS
Affects mcpmSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 2.15.0_1 soon.
Data as of 30 Oct 2026, 07:00 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.15.0_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Upgrade mcpm to 2.15.0_1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmcpmpkg:brew/mcpmOther 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
Upgrade to Starlette version 2.15.0_1 or later, which enforces max_fields and max_part_size limits on application/x-www-form-urlencoded parsing. The patched parser raises errors before excessive fields or large field sizes are accumulated. Configure max_fields and max_part_size as needed, with defaults matching multipart/form-data limits (max_fields=1000, max_part_size=1MB).
Description
Starlette's request.form() method does not enforce configured limits on max_fields and max_part_size for application/x-www-form-urlencoded content types, allowing unauthenticated attackers to send requests with extremely large numbers of fields or very large field sizes. This leads to denial of service by blocking the event loop or causing excessive memory allocation. The issue is fixed in version 2.15.0_1 by properly enforcing these limits during parsing.