Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
LiteLLM versions before 1.83.14 are affected. An authenticated internal_user can create an API key with access to routes their role does not permit, because the allowed_routes field is stored without checking it against the user's own permissions. The key can then reach admin-only routes, allowing privilege escalation to proxy_admin. Upgrade litellm to 1.83.14 or later.
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 |
|---|---|---|---|---|
| 8.7 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N | CNA (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.012, the 68th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 21 May 2026, 20:33 UTC Confirmed by the CVE List
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qrc4-49gv-mv9m
- OSV: GHSA-qrc4-49gv-mv9m
- nvd.nist.gov/vuln/detail/CVE-2026-47101
- github.com/BerriAI/litellm/commit/2220f3076ac89bd2a2e3439acf57dcfbec2434c9
- github.com/BerriAI/litellm/commit/5190bd07eb23a037745d86328096f54378f1614a
- github.com/BerriAI/litellm/commit/d910a95661fce3cdd36f3b06c03ecf9c46c6457c
- gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827f
- github.com/BerriAI/litellm
- github.com/BerriAI/litellm/releases/tag/v1.83.14-stable
- huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9
- www.obsidiansecurity.com/blog/litellm-privilege-escalation-rce
- www.vulncheck.com/advisories/litellm-privilege-escalation-via-api-key-generation