PT-2026-53476 · Pypi · Litellm

Published 2026-06-29 · Updated 2026-06-29

OSV

CVSS v3.1

9.8

Critical

Base vector

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

Discovery Credit: Tencent YunDing Security Lab

Fix

Related Identifiers

PYSEC-2026-391

Affected Products

Litellm

References · 8

• https://nvd.nist.gov/vuln/detail/CVE-2026-42208 · Security Note
• https://osv.dev/vulnerability/PYSEC-2026-391 · Vendor Advisory
• https://github.com/BerriAI/litellm · Note
• https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc · Note
• https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable · Note
• https://github.com/advisories/GHSA-r75f-5x8p-qvmc · Note
• https://cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42208 · Note
• https://pypi.org/project/litellm · Note