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.
CVE-2026-47101
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-21. A secondary CVSS source baseline 8.8; sources differ by 0.0.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%The EG Score, 8.8 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.3%
- EPSS %ILE
- 70th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 21, 2026
Last Modified
October 8, 2026
Advisory Details (7)
Auto-updated May 22, 2026LiteLLM < 1.83.14 Privilege Escalation via API Key Generation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/litellm-privilege-escalation-via-api-key-generationhuntr - The world’s first bug bounty platform for AI/ML
https://huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9Release v1.83.14-stable · BerriAI/litellm · GitHub
https://github.com/BerriAI/litellm/releases/tag/v1.83.14-stablefix(proxy): improve input validation on management endpoints · BerriAI/litellm@d910a95 · GitHub
https://github.com/BerriAI/litellm/commit/d910a95661fce3cdd36f3b06c03ecf9c46c6457cfix: extend caller-permission checks to service-account + harden raw-… · BerriAI/litellm@5190bd0 · GitHub
https://github.com/BerriAI/litellm/commit/5190bd07eb23a037745d86328096f54378f1614afix: tighten caller-permission checks on key route fields · BerriAI/litellm@2220f30 · GitHub
https://github.com/BerriAI/litellm/commit/2220f3076ac89bd2a2e3439acf57dcfbec2434c9LiteLLM-Privilege-Escalation.md · GitHub
https://gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827fVendor Advisories for CVE-2026-47101(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| litellm | 0.1.0 ... 1.9.dev0 (1115 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 28× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 99 of 208 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-11 19:45 UTCEG score recompute
- 2026-10-11 16:59 UTCEG score recompute
- 2026-10-11 14:24 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-08 16:41 UTCEG score recompute
- 2026-10-08 15:47 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.3% · 70th percentile
- 2026-09-30 02:40 UTCOSV refresh
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.2% · 66th percentile
Show 74 moreShow fewer
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-11 04:23 UTCOSV refresh
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-23 16:47 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-21 21:44 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-20 18:43 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-16 16:50 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-16 03:22 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-15 03:42 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-14 01:55 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-12 22:41 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-11 13:47 UTCEG score recompute
- 2026-08-11 00:30 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-09 14:17 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-09 01:26 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-08 02:34 UTCEG score recompute
- 2026-08-07 00:53 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-05 21:12 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-03 16:50 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-02 06:46 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-08-01 17:24 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-29 17:41 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-28 02:22 UTCEG score recompute
- 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-26 08:09 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:litellm
- CVE-2026-37004EG 9.8CRITICAL
- CVE-2026-12773EG 9.8CRITICAL
- CVE-2026-49468EG 9.8CRITICAL
- CVE-2026-42208EG 9.8 KEVEPSS p93CRITICAL
- CVE-2024-5751EG 9.8CRITICAL
- CVE-2024-4264EG 9.8CRITICAL
- CVE-2024-2952EG 9.8CRITICAL
- CVE-2026-35030EG 9.1CRITICAL
- CVE-2026-59822NVD 8.2EG 9.0 KEVCRITICAL
- CVE-2026-42271NVD 8.8EG 9.0 KEVEPSS p100CRITICAL
Frequently asked(5)
What is CVE-2026-47101?
When was CVE-2026-47101 made public?
Is CVE-2026-47101 actively exploited?
What is the CVSS score of CVE-2026-47101?
How do I remediate CVE-2026-47101?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47101
Is Your Infrastructure Affected by CVE-2026-47101?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.