LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47102: LiteLLM < 1.83.10 Privilege Escalation via User Update

LiteLLM prior to 1.83.10 allows a user to modify their own user_role via the /user/update endpoint. While the endpoint correctly restricts users to updating only their own account, it does not restrict which fields may be changed. A user who can reach this endpoint can set their role to proxy_admin, gaining full administrative access to LiteLLM including all users, teams, keys, models, and prompt history. Users with the org_admin role have legitimate access to this endpoint and can exploit this vulnerability without chaining any additional flaw.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

LiteLLM versions before 1.83.10 let an eligible user promote their own account to proxy administrator. That role provides control over users, teams, keys, models, and prompt history, creating substantial confidentiality, integrity, and availability risk.

Executive priority

Prioritize remediation immediately for affected production or externally reachable deployments. The flaw converts limited authorized access into complete platform administration, potentially exposing credentials and sensitive AI activity. Investigate for unauthorized role changes alongside upgrading.

Technical view

The /user/update endpoint verifies that users modify only their own account but insufficiently restricts writable fields. A caller able to use the endpoint can change user_role to proxy_admin. Exploitation requires low privileges, no user interaction, and no additional flaw for org_admin users. CVSS 3.1 rates it 8.8.

Likely exposure

Deployments running LiteLLM earlier than 1.83.10 are potentially exposed when untrusted or insufficiently trusted users can reach /user/update. The bundle specifically confirms that org_admin users have legitimate endpoint access. Internet exposure may increase opportunity, but it is not required.

Exploitation context

Public technical descriptions and exploit references exist, so defenders should assume the technique is reproducible. However, the supplied record is not in KEV and provides no evidence of active exploitation in the wild.

Researcher notes

The issue aligns with CWE-863 and CWE-915: authorization exists at the object level, but privileged field assignment remains uncontrolled. The decisive exposure question is which roles can call /user/update. Public exploit material exists, but the bundle does not establish real-world exploitation or compromise prevalence.

Mitigation direction

  • Upgrade LiteLLM to version 1.83.10 or later using vendor release guidance.
  • Until upgraded, restrict /user/update access to the smallest trusted administrator group.
  • Review users for unexpected proxy_admin assignments and revoke unauthorized privileges.
  • Rotate exposed keys and credentials if investigation identifies unauthorized administrative access.

Validation and detection

  • Inventory every LiteLLM deployment and confirm its running version, not merely its configured package version.
  • Verify /user/update rejects attempts to modify user_role or other privileged fields.
  • Audit user-role changes for unexplained promotions to proxy_admin.
  • Review administrative access to users, teams, keys, models, and prompt history.
Prepared
Confidence
high
Sources
6

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 · 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
cwe · low confidence lookup

CWE-915: 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
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-47102 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:NVulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-47102Attack 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 through user role modification
other:Red Hat severity ratingcvssV3_1
  • 2026-05-21T21:00:51.047Z: Reported to Red Hat.
  • 2026-05-21T20:34:37.893Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BerriAIlitellm0affected
Weakness

CWE details

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

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.

CWE-915 · source CWE mapping

Improperly Controlled Modification of Dynamically-Determined Object Attributes

Improperly Controlled Modification of Dynamically-Determined Object Attributes represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.