chore(deps): update dependency python-multipart to v0.0.27 [security]#1596
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency python-multipart to v0.0.27 [security]#1596renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
d2fc126 to
1b8477c
Compare
6bd022b to
21d28e5
Compare
93504e8 to
fa2b61b
Compare
8408491 to
c0e3bef
Compare
456852f to
e331fb7
Compare
ebc6813 to
3d9559e
Compare
cd5bc08 to
dc21080
Compare
dc21080 to
941d159
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==0.0.22→==0.0.27python-multipart affected by Denial of Service via large multipart preamble or epilogue data
CVE-2026-40347 / GHSA-mj87-hwqh-73pj
More information
Details
Summary
A denial of service vulnerability exists when parsing crafted
multipart/form-datarequests with large preamble or epilogue sections.Details
Two inefficient multipart parsing paths could be abused with attacker-controlled input.
Before the first multipart boundary, the parser handled leading CR and LF bytes inefficiently while searching for the start of the first part. After the closing boundary, the parser continued processing trailing epilogue data instead of discarding it immediately. As a result, parsing time could grow with the size of crafted data placed before the first boundary or after the closing boundary.
Impact
An attacker can send oversized malformed multipart bodies that consume excessive CPU time during request parsing, reducing request-handling capacity and delaying legitimate requests. This issue degrades availability but does not typically result in a complete denial of service for the entire application.
Mitigation
Upgrade to version
0.0.26or later, which skips ahead to the next boundary candidate when processing leading CR/LF data and immediately discards epilogue data after the closing boundary.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
python-multipart has Denial of Service via unbounded multipart part headers
CVE-2026-42561 / GHSA-pp6c-gr5w-3c5g
More information
Details
Summary
python-multiparthas a denial of service vulnerability in multipart part header parsing. When parsingmultipart/form-data,MultipartParserpreviously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.Impact
Applications that parse attacker-controlled
multipart/form-datawith affected versions ofpython-multipartcan experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invokepython-multipartmay have worker or event-loop delays while processing malicious upload requests.Details
The affected parser states are
HEADER_FIELD_START,HEADER_FIELD,HEADER_VALUE_START,HEADER_VALUE, andHEADER_VALUE_ALMOST_DONE. The issue can be triggered by:Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.
Mitigation
Upgrade to
python-multipart0.0.27or later.If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of
python-multipartstill parse multipart part headers without the default header count and header size limits.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
python-multipart affected by Denial of Service via large multipart preamble or epilogue data
CVE-2026-40347 / GHSA-mj87-hwqh-73pj
More information
Details
Summary
A denial of service vulnerability exists when parsing crafted
multipart/form-datarequests with large preamble or epilogue sections.Details
Two inefficient multipart parsing paths could be abused with attacker-controlled input.
Before the first multipart boundary, the parser handled leading CR and LF bytes inefficiently while searching for the start of the first part. After the closing boundary, the parser continued processing trailing epilogue data instead of discarding it immediately. As a result, parsing time could grow with the size of crafted data placed before the first boundary or after the closing boundary.
Impact
An attacker can send oversized malformed multipart bodies that consume excessive CPU time during request parsing, reducing request-handling capacity and delaying legitimate requests. This issue degrades availability but does not typically result in a complete denial of service for the entire application.
Mitigation
Upgrade to version
0.0.26or later, which skips ahead to the next boundary candidate when processing leading CR/LF data and immediately discards epilogue data after the closing boundary.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
python-multipart has Denial of Service via unbounded multipart part headers
CVE-2026-42561 / GHSA-pp6c-gr5w-3c5g
More information
Details
Summary
python-multiparthas a denial of service vulnerability in multipart part header parsing. When parsingmultipart/form-data,MultipartParserpreviously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.Impact
Applications that parse attacker-controlled
multipart/form-datawith affected versions ofpython-multipartcan experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invokepython-multipartmay have worker or event-loop delays while processing malicious upload requests.Details
The affected parser states are
HEADER_FIELD_START,HEADER_FIELD,HEADER_VALUE_START,HEADER_VALUE, andHEADER_VALUE_ALMOST_DONE. The issue can be triggered by:Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.
Mitigation
Upgrade to
python-multipart0.0.27or later.If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of
python-multipartstill parse multipart part headers without the default header count and header size limits.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
Kludex/python-multipart (python-multipart)
v0.0.27Compare Source
v0.0.26Compare Source
v0.0.25Compare Source
File#143.FormParserclasses #257.UPLOAD_DELETE_TMPtoFormParserconfig #254.field_endfor trailing bare field names on finalize #230.v0.0.24Compare Source
chunk_sizeinparse_form()#244.v0.0.23Compare Source
trust_x_headersparameter andX-File-Namefallback #196.QuerystringParser._internal_write#229.__init__.py#227.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.