<?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-30T03:55:44.017320+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-40217</id>
    <title>CVE-2026-40217</title>
    <updated>2026-09-30T03:55:44.035601+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> BerriAI LiteLLM, Red Hat Ansible Automation Platform 2.6, Red Hat OpenShift AI 3.3, Red Hat Lightspeed Core, Red Hat OpenShift AI (RHOAI)</p>
<p>LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-40217"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-wxxx-gvqv-xp7p</id>
    <title>GHSA-wxxx-gvqv-xp7p — LiteLLM has a sandbox escape in custom-code guardrail</title>
    <updated>2026-09-30T03:55:44.035715+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>The `POST /guardrails/test_custom_code` endpoint runs user-supplied Python inside a hand-rolled sandbox. The sandbox can be escaped using bytecode-level techniques, allowing arbitrary code execution in the proxy process — which runs as root in the default Docker image.</p>
<p>**Reaching the endpoint requires a proxy-admin credential** in default configurations.</p>
<p>### Patches</p>
<p>Fixed in **`1.83.11`**. The hand-rolled sandbox has been replaced with `RestrictedPython`. Upgrade to `1.83.11` or later.</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible, block `POST /guardrails/test_custom_code` at your reverse proxy or API gateway.</p>
<p>### References</p>
<p>- Patched release: [`v1.83.10-stable`](https://github.com/BerriAI/litellm/releases/tag/v1.83.10-stable)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-wxxx-gvqv-xp7p"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-2601</id>
    <title>PYSEC-2026-2601 — LiteLLM has a sandbox escape in custom-code guardrail</title>
    <updated>2026-09-30T03:55:44.035787+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>The `POST /guardrails/test_custom_code` endpoint runs user-supplied Python inside a hand-rolled sandbox. The sandbox can be escaped using bytecode-level techniques, allowing arbitrary code execution in the proxy process — which runs as root in the default Docker image.</p>
<p>**Reaching the endpoint requires a proxy-admin credential** in default configurations.</p>
<p>### Patches</p>
<p>Fixed in **`1.83.11`**. The hand-rolled sandbox has been replaced with `RestrictedPython`. Upgrade to `1.83.11` or later.</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible, block `POST /guardrails/test_custom_code` at your reverse proxy or API gateway.</p>
<p>### References</p>
<p>- Patched release: [`v1.83.10-stable`](https://github.com/BerriAI/litellm/releases/tag/v1.83.10-stable)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-2601"/>
  </entry>
</feed>
