CVE-2026-47102
Litellm broken access control
- Published21 May 2026
Description
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.
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-47102
- https://bugzilla.redhat.com/show_bug.cgi?id=2480634
- https://gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827f
- https://github.com/BerriAI/litellm/commit/128d32d2494b759c5d15da3452452af4c6a34c01
- https://github.com/BerriAI/litellm/commit/e6f18ce75b111c9b93dc15c72894cbdeb53177ce
- https://github.com/BerriAI/litellm/pull/25541
- https://github.com/BerriAI/litellm/releases/tag/v1.83.10-stable
- https://huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-47102.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-47102 being actively exploited?
CVE-2026-47102 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.82%.
How severe is CVE-2026-47102?
CVE-2026-47102 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.82% probability of exploitation.
Which products are affected by CVE-2026-47102?
Affected products include Litellm.
How do I fix CVE-2026-47102?
Upgrade affected software to a fixed version, for example Litellm 1.83.10 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-47102 against the real software inventory on every managed device, every day. 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.