https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T19:52:53.318504+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/brew-rawdog-cve-2026-42208 BREW-rawdog-CVE-2026-42208 — LiteLLM has SQL Injection in Proxy API key verification 2026-10-03T19:52:53.412925+00:00

Affected: Homebrew: rawdog

### Impact

A database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing it as a separate parameter. An unauthenticated attacker could send a specially crafted `Authorization` header to any LLM API route (for example `POST /chat/completions`) and reach this query through the proxy's error-handling path.

An attacker could read data from the proxy's database and may be able to modify it, leading to unauthorised access to the proxy and the credentials it manages.

### Patches

Fixed in **`1.83.7`**. The caller-supplied value is now always passed to the database as a separate parameter. Upgrade to `1.83.7` or later.

### Workarounds

If upgrading is not immediately possible, set `disable_error_logs: true` under `general_settings`. This removes the path through which unauthenticated input reaches the vulnerable query.

### References

- Patched release: [`v1.83.7-stable`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable)

**Discovery Credit**: Tencent YunDing Security Lab

 https://cve.radiocsirt.org/vuln/euvd-2026-337245 EUVD-2026-337245 2026-10-03T19:52:53.412991+00:00 EUVD-2026-337245 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42208 fkie_cve-2026-42208 2026-10-03T19:52:53.413009+00:00

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From version 1.81.16 to before version 1.83.7, a database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing it as a separate parameter. An unauthenticated attacker could send a specially crafted Authorization header to any LLM API route (for example POST /chat/completions) and reach this query through the proxy's error-handling path. An attacker could read data from the proxy's database and may be able to modify it, leading to unauthorised access to the proxy and the credentials it manages. This issue has been patched in version 1.83.7.

 https://cve.radiocsirt.org/vuln/ghsa-r75f-5x8p-qvmc GHSA-r75f-5x8p-qvmc — LiteLLM has SQL Injection in Proxy API key verification 2026-10-03T19:52:53.413037+00:00

Affected: PyPI: litellm

### Impact

A database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing it as a separate parameter. An unauthenticated attacker could send a specially crafted `Authorization` header to any LLM API route (for example `POST /chat/completions`) and reach this query through the proxy's error-handling path.

An attacker could read data from the proxy's database and may be able to modify it, leading to unauthorised access to the proxy and the credentials it manages.

### Patches

Fixed in **`1.83.7`**. The caller-supplied value is now always passed to the database as a separate parameter. Upgrade to `1.83.7` or later.

### Workarounds

If upgrading is not immediately possible, set `disable_error_logs: true` under `general_settings`. This removes the path through which unauthenticated input reaches the vulnerable query.

### References

- Patched release: [`v1.83.7-stable`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable)

**Discovery Credit**: Tencent YunDing Security Lab

 https://cve.radiocsirt.org/vuln/ncsc-2026-0137 NCSC-2026-0137 — Kwetsbaarheden verholpen in LiteLLM door BerriAI 2026-10-03T19:52:53.413069+00:00 NCSC-2026-0137 https://cve.radiocsirt.org/vuln/pysec-2026-391 PYSEC-2026-391 — LiteLLM has SQL Injection in Proxy API key verification 2026-10-03T19:52:53.413090+00:00

Affected: PyPI: litellm

### Impact

A database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing it as a separate parameter. An unauthenticated attacker could send a specially crafted `Authorization` header to any LLM API route (for example `POST /chat/completions`) and reach this query through the proxy's error-handling path.

An attacker could read data from the proxy's database and may be able to modify it, leading to unauthorised access to the proxy and the credentials it manages.

### Patches

Fixed in **`1.83.7`**. The caller-supplied value is now always passed to the database as a separate parameter. Upgrade to `1.83.7` or later.

### Workarounds

If upgrading is not immediately possible, set `disable_error_logs: true` under `general_settings`. This removes the path through which unauthenticated input reaches the vulnerable query.

### References

- Patched release: [`v1.83.7-stable`](https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable) **Discovery Credit**: Tencent YunDing Security Lab

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1288 WID-SEC-W-2026-1288 — LiteLLM: Mehrere Schwachstellen 2026-10-03T19:52:53.413120+00:00

Ein Angreifer kann mehrere Schwachstellen in LiteLLM ausnutzen, um einen SQL-Injection-Angriff durchzuführen und sich unbefugten Zugriff zu verschaffen oder um beliebigen Programmcode mit den Rechten des Dienstes auszuführen