CVE-2026-47101
Litellm broken access control
- Published21 May 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-47101
- https://bugzilla.redhat.com/show_bug.cgi?id=2480635
- https://gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827f
- https://github.com/BerriAI/litellm/commit/2220f3076ac89bd2a2e3439acf57dcfbec2434c9
- https://github.com/BerriAI/litellm/commit/5190bd07eb23a037745d86328096f54378f1614a
- https://github.com/BerriAI/litellm/commit/d910a95661fce3cdd36f3b06c03ecf9c46c6457c
- https://github.com/BerriAI/litellm/releases/tag/v1.83.14-stable
- https://huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-47101.json
- https://www.obsidiansecurity.com/blog/litellm-privilege-escalation-rce
and 1 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-47101 being actively exploited?
CVE-2026-47101 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.33%.
How severe is CVE-2026-47101?
CVE-2026-47101 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 1.33% probability of exploitation.
Which products are affected by CVE-2026-47101?
Affected products include Litellm.
How do I fix CVE-2026-47101?
Upgrade affected software to a fixed version, for example Litellm 1.83.14 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-47101 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.