GHSA-wpfp-gwwc-vwq6 is a high-severity (CVSS 8.8) CWE-863 vulnerability in litellm. A fix is available for litellm — see the affected versions and patch details below.
LiteLLM allows a user to modify their own user_role via the /user/update endpoint
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-wpfp-gwwc-vwq6.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-wpfp-gwwc-vwq6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,205 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
litellmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
LiteLLM prior to 1.83.10 allows a user to modify their own user_role via the /user/update endpoint. While the endpoint correctly restricts users to updating only their own account, it does not restrict which fields may be changed. A user who can reach this endpoint can set their role to proxy_admin, gaining full administrative access to LiteLLM including all users, teams, keys, models, and prompt history. Users with the org_admin role have legitimate access to this endpoint and can exploit this vulnerability without chaining any additional flaw.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | litellm | all versions | 1.83.10pip install --upgrade 'litellm==1.83.10' |
Affected Products
litellmlitellmDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for litellm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update litellm to 1.83.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wpfp-gwwc-vwq6 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated Important because an authenticated LiteLLM proxy user may be able to modify their own user_role via the /user/update endpoint and escalate to proxy_admin, gaining full administrative access to the LiteLLM instance. Exploitation requires network access to a LiteLLM proxy deployment and valid…
Update the litellm package to version 1.83.10 or later. Until updated builds are available, restrict access to LiteLLM proxy /user/update and /user/bulk_update endpoints so only trusted administrators can modify user accounts. Audit user_role assignments for unexpected proxy_admin promotions.Source: Red Hat security advisory for GHSA-wpfp-gwwc-vwq6 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-wpfp-gwwc-vwq6 in your dependencies?
Find it across PyPI, including transitive dependencies.