deps(security): bump litellm floor to >=1.83.7 (5 GHSA: 2 CRITICAL + 3 HIGH)

[r266-tech]

Summary

Raise litellm floor in pyproject.toml from >=1.0.0 to >=1.83.7 to close five GHSA advisories. The existing ceiling <1.83.13 is unchanged.

Vulnerabilities

Advisory	Severity	Affected	First patched
GHSA-r75f-5x8p-qvmc	CRITICAL	>=1.81.16,<1.83.7	1.83.7
GHSA-jjhc-v7c2-5hh6	CRITICAL	<1.83.0	1.83.0
GHSA-v4p8-mg3p-g94g	HIGH	>=1.74.2,<1.83.7	1.83.7
GHSA-xqmj-j6mv-4862	HIGH	>=1.80.5,<1.83.7	1.83.7
GHSA-69x8-hrgq-fjj8	HIGH	<1.83.0	1.83.0

>=1.83.7 is the smallest floor that closes all five. CRITICAL items are SQL injection in proxy API-key verification (auth surface) and OIDC userinfo cache-key collision auth bypass; HIGH items are authenticated RCE via MCP stdio test endpoints, SSTI in /prompts/test, and password-hash exposure / pass-the-hash bypass.

Diff

-    "litellm>=1.0.0,<1.83.13",
+    "litellm>=1.83.7,<1.83.13",

Notes

• <1.83.13 ceiling kept as-is. 1.83.7 is well below the ceiling; no resolver math change.
• uv.lock not regenerated in this PR, matching Dependabot precedent (build(deps): update litellm requirement from <1.83.9,>=1.0.0 to >=1.0.0,<1.83.13 #1670, build(deps): update litellm requirement from <1.83.1,>=1.0.0 to >=1.0.0,<1.83.9 #1496, build(deps): update litellm requirement from <1.83.13,>=1.83.7 to >=1.83.7,<1.83.15 #1829 — all litellm-related PRs only touched pyproject.toml). Locked-install users will pick up the new floor on the next uv lock. Happy to add a uv.lock regen commit if maintainers prefer it in-band.
• Sibling Dependabot PR build(deps): update litellm requirement from <1.83.13,>=1.83.7 to >=1.83.7,<1.83.15 #1829 raises the ceiling (<1.83.13 → <1.83.15), orthogonal to this floor bump. Whichever lands second will need a one-line rebase; I'll handle the rebase if this lands first, or update on top of build(deps): update litellm requirement from <1.83.13,>=1.83.7 to >=1.83.7,<1.83.15 #1829.
• No competing OPEN PR for litellm floor (verified via gh pr list).
• Companion PR deps: bump python-multipart >=0.0.27 (GHSA-pp6c-gr5w-3c5g, CVSS 7.5 DoS) #1877 applied the same pattern to python-multipart (GHSA-pp6c-gr5w-3c5g).

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ❌ 1670 - Partially compliant Compliant requirements: litellm ceiling is <1.83.13 Non-compliant requirements: litellm floor is now >=1.83.7 (exceeds ticket's >=1.0.0, but addresses more vulnerabilities) 1496 - Not compliant Non-compliant requirements: litellm ceiling is <1.83.13 (exceeds ticket's <1.83.9) litellm floor is >=1.83.7 (exceeds ticket's >=1.0.0) 1877 - Not compliant Non-compliant requirements: python-multipart still at >=0.0.22

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 85

🧪 No relevant tests

🔒 Security concerns Unpatched vulnerability: python-multipart remains at >=0.0.22, which is affected by GHSA-pp6c-gr5w-3c5g (Denial of Service via unbounded multipart part headers).

✅ No TODO sections

🔀 No multiple PR themes

⚡ Recommended focus areas for review Missing Dependency Bump python-multipart is still at >=0.0.22, which is vulnerable to GHSA-pp6c-gr5w-3c5g (CVSS 7.5 DoS). It should be bumped to >=0.0.27 as requested in ticket "python-multipart>=0.0.22",

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.