LiteLLM prior to 1.83.14 allows an authenticated internal_user to create API keys with access to routes that their role does not permit. When generating a key, the allowed_routes field is stored without verifying that the specified routes fall within the user's own permissions. A key created with access to admin-only routes can then be used to reach those routes successfully, bypassing the role-based access controls that would otherwise block the request, enabling full privilege escalation from internal_user to proxy_admin.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Thu, 21 May 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LiteLLM prior to 1.83.14 allows an authenticated internal_user to create API keys with access to routes that their role does not permit. When generating a key, the allowed_routes field is stored without verifying that the specified routes fall within the user's own permissions. A key created with access to admin-only routes can then be used to reach those routes successfully, bypassing the role-based access controls that would otherwise block the request, enabling full privilege escalation from internal_user to proxy_admin. | |
| Title | LiteLLM < 1.83.14 Privilege Escalation via API Key Generation | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-05-21T20:33:30.163Z
Reserved: 2026-05-18T19:22:26.748Z
Link: CVE-2026-47101
No data.
Status : Received
Published: 2026-05-21T21:16:32.413
Modified: 2026-05-21T21:16:32.413
Link: CVE-2026-47101
No data.
OpenCVE Enrichment
No data.
Weaknesses