Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
LiteLLM versions before 1.83.0 are affected by a chain of issues that lets an authenticated user take over another account. Password hashes are unsalted SHA-256 and are returned by several API endpoints to any authenticated user, and the login endpoint accepts the raw hash as a password, so an attacker can log in as another user and escalate privileges. Upgrade to LiteLLM 1.83.0, which uses scrypt hashing, removes hashes from API responses, and migrates existing hashes on next login.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| Not published | None | 4.0 | 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 | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:34 UTC First seen by agentprime
- 31 Oct 2026, 14:34 UTC Confirmed by OSV