litellm - 💡(How to fix) Fix [Bug]: fix critical CVE-2026-24486 and CVE-2025-67221 [2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25284Fetched 2026-04-08 03:02:10
View on GitHub
Comments
2
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
commented ×2labeled ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

The cryptography, fastapi_sso, orjson, and python-multipart packages need to be updated to the latest versions. The versions listed in the current dependencies are vulnerable:

https://nvd.nist.gov/vuln/detail/CVE-2026-24486 https://nvd.nist.gov/vuln/detail/CVE-2025-67221 https://nvd.nist.gov/vuln/detail/CVE-2025-14556 https://nvd.nist.gov/vuln/detail/CVE-2026-26007

Steps to Reproduce

Relevant log output

What part of LiteLLM is this about?

No response

What LiteLLM version are you on ?

v1.83.4

Twitter / LinkedIn details

No response

extent analysis

TL;DR

Update the cryptography, fastapi_sso, orjson, and python-multipart packages to the latest versions to address known vulnerabilities.

Guidance

  • Review the provided CVE links to understand the vulnerabilities in the current package versions.
  • Update the dependencies in your project to use the latest versions of the affected packages.
  • Verify the updates by checking the package versions in your project and ensuring they match the latest available versions.
  • Consider monitoring the project's dependencies for future vulnerabilities and updates.

Example

No code snippet is provided as the issue is related to package updates rather than code changes.

Notes

The provided information does not specify the exact latest versions of the packages, so it is recommended to check the package repositories or documentation for the most up-to-date version information.

Recommendation

Apply workaround: Update the affected packages to the latest versions to mitigate the known vulnerabilities, as the issue implies that the current versions are vulnerable and need to be updated.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: fix critical CVE-2026-24486 and CVE-2025-67221 [2 comments, 1 participants]