Update dependency python-multipart to v0.0.27 [SECURITY]#1908
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Update dependency python-multipart to v0.0.27 [SECURITY]#1908renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
renovate
Bot
force-pushed
the
renovate/pypi-python-multipart-vulnerability
branch
from
87cb39b to
8ffdfc6
Compare
renovate
Bot
force-pushed
the
renovate/pypi-python-multipart-vulnerability
branch
from
8ffdfc6 to
8987b9d
Compare
odosk
added a commit
that referenced
this pull request
May 8, 2026
Whole-manifest sweep of visual-retrieval-colpali to resolve the 18 HIGH/CRITICAL Mend findings flagged in the 2026-05-07 rescan. Notable bumps in src/legacy-requirements.txt (full sweep, not just flagged libs): accelerate 0.34.2 -> 1.13.0 (CVE-2025-14925) python-multipart 0.0.26 -> 0.0.27 (CVE-2026-42561) torch 2.8.0 -> 2.11.0 (CVE-2025-55551, CVE-2026-24747) transformers 5.0.0 -> 4.57.6 (CVE-2024-1139[2-4], CVE-2025-1492[0,1,4,6-30]) huggingface-hub 0.36.0 -> 0.36.2 tokenizers 0.20.3 -> 0.22.2 pyproject.toml: relax `transformers==5.0.0` to `>=4.57.6,<5.0.0`. The previous `==5.0.0` pin (added by Renovate PR #1903 / commit 952bb5f) was unsatisfiable because vidore-benchmark[interpretability] 4.0.x requires `transformers<5.0.0` and the application code imports `vidore_benchmark.interpretability.torch_utils` (interpretability module was removed in vidore-benchmark 5.0.0). Reverting to the latest 4.x line yields a resolvable lockfile while still picking up the silent CVE patches that landed across 4.48 -> 4.57. Pillow remains at 10.4.0 -- transitively pinned `<11.0.0` by both colpali-engine 0.3.1 and vidore-benchmark 4.0.x. Lifting it to 12.x to clear the three pillow CVEs requires migrating off vidore-benchmark[interpretability] (used by src/backend/colpali.py and prepare_feed_deploy.py); that's a code refactor and out of scope for this dep-bump PR. Supersedes Renovate PR #1908 (python-multipart 0.0.27). No local tests run; sample-apps integration tests are too heavy for a dev box. Mend rescan after merge. Related: VESPANG-3201, VESPANG-3271
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.26→==0.0.27python-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 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
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.