---
schema_version: '1.0'
id: security-20260714-3ea518
url: https://osv.dev/vulnerability/PYSEC-2026-2598
url_hash: 3ea5186ab3642830588db2ce1ff49095a7636264fd849c81365436ec0bebcc37
canonical_url: https://osv.dev/vulnerability/PYSEC-2026-2598
source: osv:pypa
category: security/library
category_raw: cve/library
region: null
tags:
- cve
- CVE-2026-47101
- PYSEC-2026-2598
- severity:CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- litellm
- PyPI
lang: en
published_at: '2026-07-13T15:19:10Z'
fetched_at: '2026-07-14T06:42:23Z'
updated_at: '2026-07-14T06:43:41Z'
status: published
content_hash: dc4c48c8cbb82f72fbff80f4200369c4b28c539b2a2ed8c7a7b673e21abadba5
license_note: full
summary: LiteLLM allows an authenticated internal_user to create API keys with access
  to routes that their role does not permit
summary_source: rss
summary_en: LiteLLM allows an authenticated internal_user to create API keys with
  access to routes that their role does not permit
entities:
- name: Tokyo Yakult Swallows
  type: organization
key_facts: []
related: []
related_auto: []
title: 'CVE-2026-47101: LiteLLM allows an authenticated internal_user to create API
  keys with access to routes that their role does not permit'
---

# CVE-2026-47101: LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit

## TL;DR
LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit

## Key Points
- cve / CVE-2026-47101 / PYSEC-2026-2598 / severity:CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H / litellm / PyPI

## Details
**Severity:** CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
**Advisory:** PYSEC-2026-2598 (CVE-2026-47101)

**Affected (your watchlist):**
- `PyPI:litellm` 1.72.6.post2 → fixed in 1.83.14 [docker/docker-strands]

**Details:**
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.

**References:**
- https://nvd.nist.gov/vuln/detail/CVE-2026-47101
- https://github.com/BerriAI/litellm/commit/2220f3076ac89bd2a2e3439acf57dcfbec2434c9
- https://github.com/BerriAI/litellm/commit/5190bd07eb23a037745d86328096f54378f1614a
- https://github.com/BerriAI/litellm/commit/d910a95661fce3cdd36f3b06c03ecf9c46c6457c
- https://gist.github.com/13ph03nix/9ec616e1fdc77b3673509c60206e827f
- https://github.com/BerriAI/litellm
- https://github.com/BerriAI/litellm/releases/tag/v1.83.14-stable
- https://huntr.com/bounties/8e75edfb-ff05-4e63-bfca-2d93d03fb3b9
- https://www.obsidiansecurity.com/blog/litellm-privilege-escalation-rce
- https://www.vulncheck.com/advisories/litellm-privilege-escalation-via-api-key-generation

_Data: OSV.dev (upstream: pypa) — https://osv.dev/vulnerability/PYSEC-2026-2598_

## Source
元記事: [CVE-2026-47101: LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit](https://osv.dev/vulnerability/PYSEC-2026-2598) — published 2026-07-13T15:19:10Z