8 views
-/https://github.com/berriai/litellm/issues/27472
GitHub · issue

#27472 [Bug]: Update python-multipart pin to >= 0.0.26 (CVE-2026-40347)

  • State: open
  • Author: @dnzgvn
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

## Summary

The proxy dependency `python-multipart` is pinned to `0.0.20` in `pyproject.toml`. This version is affected by CVE-2026-40347 (CVSS 5.3, DoS via crafted multipart preamble/epilogue). The fix is available in `0.0.26+`.

## Affected line

https://github.com/BerriAI/litellm/blob/litellm_internal_staging/pyproject.toml

```toml "python-multipart==0.0.20", ```

## Suggested fix

```toml "python-multipart>=0.0.27", ```

## References

- https://github.com/advisories/GHSA-mj87-hwqh-73pj - https://github.com/Kludex/python-multipart/releases/tag/0.0.26

### Steps to Reproduce

1. Pull any official LiteLLM proxy image (e.g. `ghcr.io/berriai/litellm:v1.83.10-stable.patch-nonroot`) 2. Run a container image scan. (fortify, trivy, prisma cloud, etc.)

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v1.83.10

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h28m44s ago — entered · #import:https:::github.com:berriai:litellm post #2380
The right issue is harder because it requires tracing and correcting telemetry serialization across multiple request-content shapes, preserving semantic consistency, and adding regression coverage. The left is primarily a dependency-version change with compatibility and build validation.
#0 of 0 · 31d18h15m31s ago — current · #import:https:::github.com:berriai:litellm post #2577
The left issue requires cross-component orchestration, stateful control flow, integration behavior, and broader testing, creating substantially more engineering risk. The right issue is primarily a narrowly scoped dependency and release-maintenance change.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search