MediumGHSA-2c2j-9gv5-cj73CVE-2025-54121PYSEC-2026-1941

Starlette has possible denial-of-service vector when parsing large files in multipart forms

Published 21 Jul 2025 · Updated 10 Sept 2026

Is your project on an affected starlette?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.47.2
Fixed in
0.47.2
Update to the fixed version for your release line, for example:pip install 'starlette>=0.47.2'

Details

Summary

When parsing a multi-part form with large files (greater than the default max spool size) starlette will block the main thread to roll the file over to disk. This blocks the event thread which means we can't accept new connections.

Details

Please see this discussion for details: https://github.com/encode/starlette/discussions/2927#discussioncomment-13721403. In summary the following UploadFile code (copied from here) has a minor bug. Instead of just checking for self._in_memory we should also check if the additional bytes will cause a rollover.


    @property
    def _in_memory(self) -> bool:
        # check for SpooledTemporaryFile._rolled
        rolled_to_disk = getattr(self.file, "_rolled", True)
        return not rolled_to_disk

    async def write(self, data: bytes) -> None:
        if self.size is not None:
            self.size += len(data)

        if self._in_memory:
            self.file.write(data)
        else:
            await run_in_threadpool(self.file.write, data)

I have already created a PR which fixes the problem: https://github.com/encode/starlette/pull/2962

PoC

See the discussion here for steps on how to reproduce.

Impact

To be honest, very low and not many users will be impacted. Parsing large forms is already CPU intensive so the additional IO block doesn't slow down starlette that much on systems with modern HDDs/SSDs. If someone is running on tape they might see a greater impact.

Is GHSA-2c2j-9gv5-cj73 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

  • HighCVE-2026-54283Starlette: request.form() limits silently ignored for application/x-www-form-urlencoded enable DoS · 15 Jun 2026
  • 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
All 10 advisories for starlette

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.