<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T23:53:26.170067+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-47101</id>
    <title>CVE-2026-47101 — LiteLLM &lt; 1.83.14 Privilege Escalation via API Key Generation</title>
    <updated>2026-09-29T23:53:26.173986+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> BerriAI litellm, Red Hat Exploit Intelligence, Red Hat Ansible Automation Platform 2, Red Hat OpenShift AI (RHOAI)</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-47101"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-qrc4-49gv-mv9m</id>
    <title>GHSA-qrc4-49gv-mv9m — LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit</title>
    <updated>2026-09-29T23:53:26.174121+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: litellm</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-qrc4-49gv-mv9m"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-2598</id>
    <title>PYSEC-2026-2598 — LiteLLM allows an authenticated internal_user to create API keys with access to routes that their role does not permit</title>
    <updated>2026-09-29T23:53:26.174172+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: litellm</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-2598"/>
  </entry>
</feed>
