Low

BerriAI litellm has Security Feature Bypass in BannedKeywords and AzureContentSafety Guardrails via call_type Mismatch on Async Endpoints

  • Disclosed: 21.06.2026
  • Updated: 11.10.2026 15:18

A security flaw has been discovered in BerriAI litellm up to 1.82.5. Affected is the function async_pre_call_hook of the file enterprise/enterprise_hooks/banned_keywords.py of the component Completions Interface. The manipulation of the argument prompt results in incorrect authorization. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) litellm <= 1.82.5 no fix

References

CVSS score 6.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Weakness (CWE)
CWE-285
Platform
Python (PyPI)
Package
litellm
Disclosed
21.06.2026
Updated
11.10.2026 15:18

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-4074 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-p897-vf7j-f5h8 - CC BY 4.0

Vulnerability history: litellm

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (42) in the archive
Total entries
42
First → latest
04.2024 09.2026
Without a fix
14
Exploited in attacks
3

Severity breakdown

  • Critical 7
  • High 17
  • Medium 8
  • Low 9
  • Unrated 1

Disclosures per year

  1. 2024: 8
  2. 2025: 6
  3. 2026: 28
Severity:
  1. High Exploited in attacks CVE-2026-59822 < 1.84.0 1.84.0
  2. BerriAI litellm has Security Feature Bypass in BannedKeywords and AzureContentSafety Guardrails via call_type Mismatch on Async Endpoints this entry
    Low · 6.3 CVE-2026-12797 <= 1.82.5 no fix
  3. Critical · 9.8 CVE-2026-49468 < 1.84.0 1.84.0
  4. High · 8.8 CVE-2026-40217 >= 1.81.8, < 1.83.10 1.83.10
  5. High · 8.8 Exploited in attacks CVE-2026-42271 >= 1.74.2, < 1.83.7 1.83.7
  6. Critical · 9.8 Exploited in attacks CVE-2026-42208 >= 1.81.16, < 1.83.7 1.83.7
  7. High CVE-2026-42203 >= 1.80.5, < 1.83.7 1.83.7
  8. Critical ghsa-5mg7-485q-xm76 >= 1.82.7, <= 1.82.8 no fix
  9. High · 8.1 CVE-2025-0628 < 1.61.15 1.61.15
  10. High · 7.5 CVE-2025-0330 <= 1.52.1 no fix
  11. High · 7.5 CVE-2024-9606 < 1.44.12 1.44.12
  12. High · 8.8 CVE-2024-6825 >= 1.40.3.dev2, <= 1.40.12 no fix
  13. High · 7.5 CVE-2024-10188 < 1.53.1.dev1 1.53.1.dev1
  14. High · 7.5 CVE-2024-6587 < 1.44.8 1.44.8
  15. Critical · 9.8 CVE-2024-5751 < 1.40.16 1.40.16
  16. High · 6.5 CVE-2024-4888 < 1.35.36 1.35.36
  17. High · 7.2 CVE-2024-4264 <= 1.28.11 no fix

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.