Browse / AI Framework and Platform Flaws / CVE-2026-47101
LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Authentication and access control
- Affected
- litellm (PyPI)
- Gets past
- Authorisation check
- CVSS
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 1.2% chance of exploitation in 30 days
How it works, in short
API keys can be issued with routes outside the creator's role, and the gateway then honours them for admin endpoints. (Our summary, written by a model. The source text is below.)
Details
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-47101
- https://github.com/BerriAI/litellm/commit/2220f3076ac89bd2a2e3439acf57dcfbec2434c9
- https://github.com/BerriAI/litellm/commit/5190bd07eb23a037745d86328096f54378f1614a
- https://github.com/BerriAI/litellm/commit/d910a95661fce3cdd36f3b06c03ecf9c46c6457c
- https://gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827f
- https://github.com/BerriAI/litellm
- https://github.com/BerriAI/litellm/releases/tag/v1.83.14-stable
- https://huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9
- https://www.obsidiansecurity.com/blog/litellm-privilege-escalation-rce
- https://www.vulncheck.com/advisories/litellm-privilege-escalation-via-api-key-generation
Source: GitHub Advisory Database, used under CC BY 4.0.