LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47101: LiteLLM < 1.83.14 Privilege Escalation via API Key Generation

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

An authenticated LiteLLM internal user can create an API key granting administrator-only routes, bypassing intended role restrictions. This can elevate the user to proxy administrator and potentially expose or alter sensitive proxy resources. LiteLLM versions before 1.83.14 are affected.

Executive priority

Prioritize remediation because a low-privileged authenticated user could gain full proxy administration with low complexity. Upgrade promptly, then investigate previously generated keys and administrator-route access. Internet exposure increases reachability, but valid internal_user credentials remain necessary.

Technical view

LiteLLM failed to verify that requested allowed_routes were within the key creator’s existing permissions. The unchecked routes were stored on newly generated keys and honored during later requests. This authorization flaw enables network-based, low-complexity privilege escalation without user interaction.

Likely exposure

Exposure requires a LiteLLM deployment earlier than 1.83.14 where an attacker already has authenticated internal_user access and can generate API keys. Environments allowing broadly distributed internal accounts or delegated key creation face greater risk.

Exploitation context

Public technical analyses and proof-of-concept references indicate the flaw is practically exploitable. However, the supplied bundle reports that it is not in KEV and provides no evidence of active exploitation in the wild.

Researcher notes

The issue maps to CWE-639 and CWE-863 and carries CVSS 3.1 score 8.8. The supplied record identifies authorization validation during API-key creation as the root cause. Patch commits and the 1.83.14 release are available; this assessment does not independently establish individual commit scope.

Mitigation direction

  • Upgrade LiteLLM to version 1.83.14 or later using vendor guidance.
  • Temporarily restrict API-key generation for untrusted internal users until upgrading.
  • Review and revoke generated keys containing routes beyond their creator’s authorized role.
  • Rotate potentially exposed administrative credentials and tokens after investigating suspicious access.

Validation and detection

  • Confirm every deployed LiteLLM instance reports version 1.83.14 or later.
  • Inventory keys created by internal users and compare allowed routes with creator permissions.
  • Review proxy logs for internal-user keys accessing administrator-only routes.
  • Verify restricted users cannot create keys granting routes outside their role after remediation.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47101 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

3CVSS vectors
5Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

3 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9VulnCheck
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-47101Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPlitellm: LiteLLM: Privilege escalation via API key generation with insufficient permission validation
other:Red Hat severity ratingcvssV3_1
  • 2026-05-21T21:00:54.938Z: Reported to Red Hat.
  • 2026-05-21T20:33:30.163Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BerriAIlitellm0affected
Weakness

CWE details

CWE-639CWE-863

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs