ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-74m5-2c7w-9w3x

MultipartParser DOS with too many fields or files

Published Feb 14, 2023 · catalog updated Feb 14, 2023 · MultipartParser DOS with too

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-74m5-2c7w-9w3x. A missing EPSS score is not a low risk. Compare MultipartParser DOS with too with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (MultipartParser DOS with too).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
pip starlette

### Impact The using the package accepts an unlimited number of multipart parts (form fields or files). Processing too many parts results in high CPU usage and high memory usage, eventually leading to an OOM process kill. This can be triggered by sending too many small form fields with no content, or too many empty files. For this to take effect application code has to: * Have installed and * call * or via another framework like FastAPI, using form field parameters or parameters, which in turn calls . ### Patches The vulnerability is solved in Starlette 0.25.0 by making the maximum fields and files customizable and with a sensible default (1000). Applications will be secure by just upgrading their Starlette version to 0.25.0 (or FastAPI to 0.92.0). If application code needs to customize the new max field and file number, there are new parameters (with the default values): * * ### Workarounds Applications that don't install or that don't use form fields are safe. In older versions, it's also possible to instead of calling call and parse the form data in internal code. In most cases, the best solution is to upgrade the Starlette version. ### References This was reported in private by @das7pad via internal email. He also coordinated the fix across multiple frameworks and parsers. The details about how is structured and parsed are in the [RFC 7578](https://www.rfc-editor.org/rfc/rfc7578).

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • pip starlette<0.25.0

How to fix GHSA-74m5-2c7w-9w3x

  • Upgrade

    GHSA-74m5-2c7w-9w3x lists a fix boundary at 0.25.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <0.25.0

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-74m5-2c7w-9w3x. A missing EPSS score is not a low risk. Compare MultipartParser DOS with too with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with <0.25.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Starlette security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 14, 2023 · Maintainer security tabs

    Detected

    ### Impact The using the package accepts an unlimited number of multipart parts (form fields or files). Processing too many parts results in high CPU usage and high memory usage, eventually leading to an OOM process kill. This can be triggered by sending too many small form fields with no content, or too many empty files. For this to take effect application code has to: * Have installed and * call

Sources

  • Maintainer security tabsVendor advisoryGHSA-74m5-2c7w-9w3x

    ### Impact The using the package accepts an unlimited number of multipart parts (form fields or files). Processing too many parts results in high CPU usage and high memory usage, eventually leading to an OOM process kill. This can be triggered by sending too many small form fields with no content, or too many empty files. For this to take effect application code has to: * Have installed and * call

    github.com

Freshness

Last verified in this catalog Feb 14, 2023. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026