<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 05:50:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-59820 — LiteLLM: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-59820</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; BerriAI litellm&lt;/p&gt;
&lt;p&gt;LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.7-stable, LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives, allowing an authenticated user with access to LiteLLM LLM API routes or a key whose allowed_routes includes /v1/skills, anthropic_routes, or llm_api_routes to upload a crafted skill archive containing path traversal entries that could be written outside the intended extraction or staging directory. This issue is fixed in version 1.83.7-stable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; BerriAI litellm&lt;/p&gt;
&lt;p&gt;LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.7-stable, LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives, allowing an authenticated user with access to LiteLLM LLM API routes or a key whose allowed_routes includes /v1/skills, anthropic_routes, or llm_api_routes to upload a crafted skill archive containing path traversal entries that could be written outside the intended extraction or staging directory. This issue is fixed in version 1.83.7-stable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-59820</guid>
    </item>
    <item>
      <title>GHSA-5jmr-gcrj-2c9q — LiteLLM: Arbitrary file write via path traversal in Skills archive extraction</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5jmr-gcrj-2c9q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: litellm&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives. An authenticated user with access to LiteLLM LLM API routes, or a key whose `allowed_routes` includes `/v1/skills`, `anthropic_routes`, or `llm_api_routes`, could upload a crafted skill archive containing path traversal entries.&lt;/p&gt;
&lt;p&gt;When the skill was processed for execution, those entries could be written outside the intended extraction/staging directory. This could allow arbitrary file write and may lead to code execution depending on deployment configuration and writable paths.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in `1.83.7-stable`.&lt;/p&gt;
&lt;p&gt;LiteLLM recommens upgrading to `1.83.7-stable` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading is not immediately possible:&lt;/p&gt;
&lt;p&gt;1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: litellm&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives. An authenticated user with access to LiteLLM LLM API routes, or a key whose `allowed_routes` includes `/v1/skills`, `anthropic_routes`, or `llm_api_routes`, could upload a crafted skill archive containing path traversal entries.&lt;/p&gt;
&lt;p&gt;When the skill was processed for execution, those entries could be written outside the intended extraction/staging directory. This could allow arbitrary file write and may lead to code execution depending on deployment configuration and writable paths.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in `1.83.7-stable`.&lt;/p&gt;
&lt;p&gt;LiteLLM recommens upgrading to `1.83.7-stable` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading is not immediately possible:&lt;/p&gt;
&lt;p&gt;1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5jmr-gcrj-2c9q</guid>
    </item>
    <item>
      <title>PYSEC-2026-3477 — LiteLLM: Arbitrary file write via path traversal in Skills archive extraction</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-3477</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: litellm&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives. An authenticated user with access to LiteLLM LLM API routes, or a key whose `allowed_routes` includes `/v1/skills`, `anthropic_routes`, or `llm_api_routes`, could upload a crafted skill archive containing path traversal entries.&lt;/p&gt;
&lt;p&gt;When the skill was processed for execution, those entries could be written outside the intended extraction/staging directory. This could allow arbitrary file write and may lead to code execution depending on deployment configuration and writable paths.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in `1.83.7-stable`.&lt;/p&gt;
&lt;p&gt;LiteLLM recommens upgrading to `1.83.7-stable` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading is not immediately possible:&lt;/p&gt;
&lt;p&gt;1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: litellm&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives. An authenticated user with access to LiteLLM LLM API routes, or a key whose `allowed_routes` includes `/v1/skills`, `anthropic_routes`, or `llm_api_routes`, could upload a crafted skill archive containing path traversal entries.&lt;/p&gt;
&lt;p&gt;When the skill was processed for execution, those entries could be written outside the intended extraction/staging directory. This could allow arbitrary file write and may lead to code execution depending on deployment configuration and writable paths.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in `1.83.7-stable`.&lt;/p&gt;
&lt;p&gt;LiteLLM recommens upgrading to `1.83.7-stable` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If upgrading is not immediately possible:&lt;/p&gt;
&lt;p&gt;1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-3477</guid>
    </item>
  </channel>
</rss>
