CVE-2026-47102

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-21. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

May 21, 2026

Last Modified

July 28, 2026

Advisory Details (7)

Auto-updated May 22, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

LiteLLM < 1.83.10 Privilege Escalation via User Update | Advisories | VulnCheck

https://www.vulncheck.com/advisories/litellm-privilege-escalation-via-user-update
generic

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9
generic

Release v1.83.10-stable · BerriAI/litellm · GitHub

https://github.com/BerriAI/litellm/releases/tag/v1.83.10-stable
generic

[Fix] Align field-level checks in user and key update endpoints by yuneng-berri · Pull Request #25541 · BerriAI/litellm · GitHub

https://github.com/BerriAI/litellm/pull/25541
generic

fix: align field-level checks in user and key update endpoints · BerriAI/litellm@e6f18ce · GitHub

https://github.com/BerriAI/litellm/commit/e6f18ce75b111c9b93dc15c72894cbdeb53177ce
generic

fix: extend field-level checks to bulk user update path · BerriAI/litellm@128d32d · GitHub

https://github.com/BerriAI/litellm/commit/128d32d2494b759c5d15da3452452af4c6a34c01
generic🟡 PoC Available

LiteLLM-Privilege-Escalation.md · GitHub

https://gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827f

Vendor Advisories for CVE-2026-47102(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)
PackageVulnerable rangeFixed inDependents
litellm0.1.0 ... 1.9.dev0 (1111 versions)1.83.10—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 166 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 16:47 UTCEG score recompute
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 21:44 UTCEG score recompute
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 18:43 UTCEG score recompute
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 16:50 UTCEG score recompute
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 03:22 UTCEG score recompute
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 03:27 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 01:55 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 15:47 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 13:47 UTCEG score recompute
  22. 2026-08-11 00:30 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 14:11 UTCEG score recompute
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 01:26 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-08 02:24 UTCEG score recompute
  4. 2026-08-07 00:53 UTCEG score recompute
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-05 21:12 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:39 UTCEPSS rescore
  10. 2026-08-03 16:50 UTCEG score recompute
  11. 2026-08-03 10:36 UTCEPSS rescore
  12. 2026-08-02 06:46 UTCEG score recompute
  13. 2026-08-02 02:27 UTCEPSS rescore
  14. 2026-08-01 17:24 UTCEG score recompute
  15. 2026-08-01 04:16 UTCEPSS rescore
  16. 2026-07-30 16:28 UTCEPSS rescore
  17. 2026-07-30 01:30 UTCEPSS rescore
  18. 2026-07-29 17:41 UTCEG score recompute
  19. 2026-07-28 15:37 UTCEPSS rescore
  20. 2026-07-28 02:22 UTCEG score recompute
  21. 2026-07-27 14:13 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 08:09 UTCEG score recompute
  25. 2026-07-25 14:18 UTCEPSS rescore
  26. 2026-07-24 14:17 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 03:17 UTCEG score recompute
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:24 UTCEPSS rescore
  31. 2026-07-20 17:08 UTCEPSS rescore
  32. 2026-07-19 14:31 UTCEPSS rescore
  33. 2026-07-19 02:29 UTCEPSS rescore
  34. 2026-07-18 10:04 UTCEPSS rescore
  35. 2026-07-17 21:59 UTCOSV refresh
  36. 2026-07-16 17:03 UTCEPSS rescore
  37. 2026-07-15 16:57 UTCEPSS rescore
  38. 2026-07-15 02:00 UTCEPSS rescore
  39. 2026-07-13 22:30 UTCEPSS rescore
  40. 2026-07-13 06:13 UTCEPSS rescore
  41. 2026-07-12 05:46 UTCEPSS rescore
  42. 2026-07-11 08:27 UTCEPSS rescore
  43. 2026-07-09 19:10 UTCEPSS rescore
  44. 2026-07-08 15:16 UTCEPSS rescore
  45. 2026-07-07 13:46 UTCEPSS rescore
  46. 2026-07-06 16:27 UTCEPSS rescore
  47. 2026-07-06 02:23 UTCEPSS rescore
  48. 2026-07-05 02:30 UTCEPSS rescore
  49. 2026-07-04 06:31 UTCEPSS rescore
  50. 2026-07-01 15:07 UTCEPSS rescore
  51. 2026-06-30 23:22 UTCEPSS rescore
  52. 2026-06-29 14:06 UTCEPSS rescore
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-28 14:07 UTCEPSS rescore
  55. 2026-06-28 04:56 UTCEPSS rescore
  56. 2026-06-28 04:56 UTCEPSS rescore
  57. 2026-06-27 03:08 UTCEPSS rescore
  58. 2026-06-25 13:49 UTCEPSS rescore
  59. 2026-06-24 14:05 UTCEPSS rescore
  60. 2026-06-23 21:33 UTCEPSS rescore
  61. 2026-06-23 21:33 UTCEPSS rescore
  62. 2026-06-22 14:25 UTCEPSS rescore
  63. 2026-06-22 14:25 UTCEPSS rescore
  64. 2026-06-21 14:56 UTCEPSS rescore
  65. 2026-06-21 14:56 UTCEPSS rescore
  66. 2026-06-21 01:59 UTCEPSS rescore
  67. 2026-06-21 01:59 UTCEPSS rescore
  68. 2026-06-19 19:26 UTCEPSS rescore
  69. 2026-06-19 19:26 UTCEPSS rescore
  70. 2026-06-18 17:52 UTCEPSS rescore
  71. 2026-06-18 17:52 UTCEPSS rescore
  72. 2026-06-17 23:53 UTCGHSA enrichment
  73. 2026-06-17 17:53 UTCEPSS rescore
  74. 2026-06-17 11:08 UTCGHSA enrichment
  75. 2026-06-16 19:42 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-47102?
CVE-2026-47102 is a high vulnerability published on May 21, 2026. LiteLLM prior to 1.83.10 allows a user to modify their own userrole 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 proxyadmin,…
When was CVE-2026-47102 disclosed?
CVE-2026-47102 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47102 actively exploited?
CVE-2026-47102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.4% of all scored CVEs.
What is the CVSS score of CVE-2026-47102?
CVE-2026-47102 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47102

Explore →

Is Your Infrastructure Affected by CVE-2026-47102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs