Skip to content

Update dependency litellm to >=1.83.0,<1.84.0 [SECURITY] - abandoned#155

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/pypi-litellm-vulnerability
Open

Update dependency litellm to >=1.83.0,<1.84.0 [SECURITY] - abandoned#155
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/pypi-litellm-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 9, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
litellm >=1.80.0,<1.82.7 → >=1.83.0,<1.84.0 age confidence

GitHub Vulnerability Alerts

CVE-2026-35029

Impact

The /config/update endpoint does not enforce admin role authorization. A user who is already authenticated into the platform can then use this endpoint to do the following:

  • Modify proxy configuration and environment variables
  • Register custom pass-through endpoint handlers pointing to attacker-controlled Python code, achieving remote code execution
  • Read arbitrary server files by setting UI_LOGO_PATH and fetching via /get_image
  • Take over other priveleged accounts by overwriting UI_USERNAME and UI_PASSWORD environment variables

Patches

Fixed in v1.83.0. The endpoint now requires proxy_admin role.

Workarounds

Restrict API key distribution. There is no configuration-level workaround.

Severity
  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N

CVE-2026-35030

Impact

When JWT authentication is enabled (enable_jwt_auth: true), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters.

This configuration option is not enabled by default. Most instances are not affected.

An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user's cached token. On cache hit, the attacker inherits the legitimate user's identity and permissions. This affects deployments with JWT/OIDC authentication enabled.

Patches

Fixed in v1.83.0. The cache key now uses the full hash of the JWT token.

Workarounds

Disable OIDC userinfo caching by setting the cache TTL to 0, or disable JWT authentication entirely.

Severity
  • CVSS Score: 9.4 / 10 (Critical)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

GHSA-69x8-hrgq-fjj8

Impact

Three issues combine into a full authentication bypass chain:

  1. Weak hashing: User passwords are stored as unsalted SHA-256 hashes, making them vulnerable to rainbow table attacks and trivially identifying users with identical passwords.
  2. Hash exposure: Multiple API endpoints (/user/info, /user/update, /spend/users) return the password hash field in responses to any authenticated user regardless of role. Plaintext passwords could also potentially be exposed in certain scenarios.
  3. Pass-the-hash: The /v2/login endpoint accepts the raw SHA-256 hash as a valid password without re-hashing, allowing direct login with a stolen

An already authenticated user can retrieve another user's password hash from the API and use it to log in as that user. This enables full privilege escalation in three HTTP requests.

Patches

Fixed in v1.83.0. Passwords are now hashed with scrypt (random 16-byte salt, n=16384, r=8, p=1). Password hashes are stripped from all API responses. Existing SHA-256 hashes are transparently migrated on next login.

Severity
  • CVSS Score: 8.6 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Release Notes

BerriAI/litellm (litellm)

v1.82.3

v1.82.1

What's Changed
New Contributors

Full Changelog: BerriAI/litellm@litellm_presidio-dev-v1.81.16...1.82.1

v1.81.13

What's Changed

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 9, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock
Command failed: uv lock --upgrade-package litellm
Using CPython 3.12.13 interpreter at: /opt/containerbase/tools/python/3.12.13/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.12.*' and platform_machine != 'x86_64' and
  │ sys_platform == 'darwin'):
  ╰─▶ Because only the following versions of litellm are available:
          litellm<=1.83.0
          litellm==1.83.1
          litellm==1.83.2
          litellm==1.83.3
          litellm==1.83.4
      and litellm==1.83.0 depends on openai>=2.8.0, we can conclude that
      litellm>=1.83.0,<1.83.1 depends on openai>=2.8.0.
      And because litellm>=1.83.1 depends on openai==2.30.0, we can conclude
      that litellm>=1.83.0 depends on openai>=2.8.0.
      And because your project depends on litellm>=1.83.0 and
      openai>=1.88.0,<2.0.0, we can conclude that your project's requirements
      are unsatisfiable.

      hint: The resolution failed for an environment that is not the current
      one, consider limiting the environments with `tool.uv.environments`.

Update deps
8cdaf68 
Signed-off-by: Nahuel Defossé <nahuel.deofsse@ibm.com>
@D3f0 D3f0 force-pushed the renovate/pypi-litellm-vulnerability branch from 7f8e05c to 8cdaf68 Compare April 15, 2026 14:46
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 15, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate Bot changed the title Update dependency litellm to >=1.83.0,<1.84.0 [SECURITY] Update dependency litellm to >=1.83.0,<1.84.0 [SECURITY] - abandoned Apr 27, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 27, 2026

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants