Starlette: request.form() limits silently ignored for application/x-www-form-urlencoded enable DoS
Published 15 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected starlette?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.4.1 <1.3.1
- Fixed in
- 1.3.1
pip install 'starlette>=1.3.1'Details
Summary
request.form() accepts max_fields and max_part_size to bound resource consumption while parsing form data. These limits are enforced for multipart/form-data, but silently ignored for application/x-www-form-urlencoded. An unauthenticated attacker can therefore send a urlencoded body with an arbitrarily large number of fields or an arbitrarily large field, even when the application configured limits it believed would apply.
Details
request.form() dispatches to a different parser depending on the Content-Type. For multipart/form-data the max_files, max_fields, and max_part_size limits are forwarded to the parser, but for application/x-www-form-urlencoded the parser is constructed without them. It has no max_fields or max_part_size parameter to receive them, and it appends every field with no count check and accumulates each field's name and value with no size check. The configured limits are therefore both unreachable and unenforced for url-encoded bodies.
Because the url-encoded parser does its work synchronously between stream reads, the two attack shapes have different effects:
- Field count drives CPU and event-loop blocking. A body of ~1,000,000 fields (a sub-10MB payload such as
f0=v&f1=v&...) blocks the worker's event loop for several seconds while parsing, during which the worker serves no other request. - Field size drives memory. A single large field value (e.g. a 50MB value) is buffered in full to build the
FormData, forcing memory allocation proportional to the request body.
The equivalent multipart/form-data request is correctly rejected with 400 Too many fields / 400 Field exceeded maximum size.
Impact
This Denial of service (DoS) vulnerability affects all applications built with Starlette (or FastAPI) that call request.form() on application/x-www-form-urlencoded requests. A single request with a very large number of fields blocks the event loop for several seconds, and a single request with a very large field forces unbounded memory allocation; in either case, parallel requests can render the service unusable. A reverse proxy that enforces a request body size limit reduces but does not eliminate the exposure, since a sub-10MB body is already enough to block the event loop.
Mitigation
Upgrade to a patched version, which forwards max_fields and max_part_size to the url-encoded parser and enforces them while parsing, raising before the oversized field or excess fields are accumulated. The defaults match multipart/form-data (max_fields=1000, max_part_size=1MB) and can be customized via request.form(max_fields=..., max_part_size=...).
Is GHSA-82w8-qh3p-5jfq in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected starlette, and gives you the command that fixes it.
More advisories for starlette
- LowCVE-2026-54282Starlette: Unvalidated request path concatenated into authority poisons request.url.hostname · 15 Jun 2026
- HighCVE-2026-48818Starlette: SSRF and NTLM credential theft via UNC paths in StaticFiles on Windows · 15 Jun 2026
- MediumCVE-2026-48817Starlette: Arbitrary HTTP method dispatched to `HTTPEndpoint` attributes via `getattr` · 15 Jun 2026
- MediumCVE-2026-48710Starlette has missing Host header validation that poisons request.url.path, bypassing path-based security checks · 4 Jun 2026
- HighCVE-2025-62727Starlette vulnerable to O(n^2) DoS via Range header merging in ``starlette.responses.FileResponse`` · 28 Oct 2025
- MediumCVE-2025-54121Starlette has possible denial-of-service vector when parsing large files in multipart forms · 21 Jul 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.