<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T20:28:38.490413+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/brew-aider-cve-2026-59820</id>
    <title>BREW-aider-CVE-2026-59820 — LiteLLM: Arbitrary file write via path traversal in Skills archive extraction</title>
    <updated>2026-10-04T20:28:38.601362+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: aider</p>
<p>### Impact</p>
<p>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.</p>
<p>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.</p>
<p>### Patches</p>
<p>The issue is fixed in `1.83.7-stable`.</p>
<p>LiteLLM recommens upgrading to `1.83.7-stable` or later.</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible:</p>
<p>1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-59820"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-335346</id>
    <title>EUVD-2026-335346</title>
    <updated>2026-10-04T20:28:38.601451+00:00</updated>
    <content>EUVD-2026-335346</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-335346"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59820</id>
    <title>fkie_cve-2026-59820</title>
    <updated>2026-10-04T20:28:38.601476+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-59820"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5jmr-gcrj-2c9q</id>
    <title>GHSA-5jmr-gcrj-2c9q — LiteLLM: Arbitrary file write via path traversal in Skills archive extraction</title>
    <updated>2026-10-04T20:28:38.601518+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: litellm</p>
<p>### Impact</p>
<p>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.</p>
<p>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.</p>
<p>### Patches</p>
<p>The issue is fixed in `1.83.7-stable`.</p>
<p>LiteLLM recommens upgrading to `1.83.7-stable` or later.</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible:</p>
<p>1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5jmr-gcrj-2c9q"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-3477</id>
    <title>PYSEC-2026-3477 — LiteLLM: Arbitrary file write via path traversal in Skills archive extraction</title>
    <updated>2026-10-04T20:28:38.601594+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: litellm</p>
<p>### Impact</p>
<p>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.</p>
<p>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.</p>
<p>### Patches</p>
<p>The issue is fixed in `1.83.7-stable`.</p>
<p>LiteLLM recommens upgrading to `1.83.7-stable` or later.</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible:</p>
<p>1. Block `POST /v1/skills` at your reverse proxy or API gateway.
2. Restrict Skills API access to trusted users only.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-3477"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2263</id>
    <title>WID-SEC-W-2026-2263 — LiteLLM: Mehrere Schwachstellen</title>
    <updated>2026-10-04T20:28:38.601660+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in LiteLLM ausnutzen, um Informationen offenzulegen, Daten zu manipulieren, Code auszuführen und um Sicherheitsmaßnahmen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2263"/>
  </entry>
</feed>
