S4E just found a high-severity finding from cve-2026-42945 scanner (version based)
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Jun 1, 2026

CVE-2026-42208 Scanner

CVE-2026-42208 Scanner - SQL Injection vulnerability in LiteLLM

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.4k
Times Used
continuous scan runs
4.1k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
🔴
CISA Known Exploited Vulnerability
This CVE is actively exploited in the wild. CISA mandates federal agencies to patch immediately.
CVECVE-2026-42208
9.3
CVSScritical
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
litellmby BerriAI
>= 1.81.16, < 1.83.7
Lightspeed Coreby Red Hat
Red Hat Ansible Automation Platform 2by Red Hat
Red Hat OpenShift AI (RHOAI)by Red Hat
Updated Aug 22, 2026View on NVD →
Detail

LiteLLM is utilized by developers and companies to manage API key checks and handle database queries efficiently. It is commonly used in environments where AI models are integrated into chat applications, providing streamlined access to model outputs. The software is known for its ease of use and integration capabilities, catering to a wide range of applications in customer service and content generation. Its flexibility and robustness make it a preferred choice for enterprises needing a reliable translation of complex inputs. As a product, LiteLLM's design focuses on handling multiple requests simultaneously, maintaining performance across different platforms. Organizations benefit from its modular API structure, which allows for easy customization and scaling according to business needs.

A SQL Injection vulnerability is detected in LiteLLM versions 1.81.16 to < 1.83.7, impacting API key verification processes. This vulnerability allows unauthenticated attackers to exploit improperly handled database keys in proxy API during key checks. By manipulating these keys, attackers can read and modify critical database data, leading to unauthorized data access. The vulnerability is critical due to the potential extent of data that could be compromised. It demonstrates the risks associated with improperly sanitized input fields in database queries. The importance of securing database queries against unauthorized manipulation is highlighted by this vulnerability.

The technical mechanism of this vulnerability involves exploiting the Authorization header field used in database query statements. Attackers can craft malicious payloads that affect SQL query execution, using 'OR' statements that interfere with normal logic flow. This allows them to execute additional queries such as 'SELECT' or use time-based SQL injections to infer database structures. The use of 'pg_sleep()' demonstrates potential exploitation aimed at bypassing initial authentication layers. By delaying responses and extracting data over subsequent requests, attackers gain actionable insights into the database schema.

Exploitation of this vulnerability could lead to compromising sensitive user information and credentials stored in affected databases. It allows attackers to achieve arbitrary command execution and unauthorized access to backend systems. Companies using vulnerable versions of LiteLLM might face severe data breaches impacting customer privacy and financial losses. The potential for data modification further exacerbates the risk, paving the way for long-term security risks. End users could experience denial of service if critical databases are hijacked and exploited. Overall, improper database query handling can expose businesses to statutory compliance issues and brand reputation damage.

REFERENCES

Solution Advice
  • Upgrade LiteLLM to version 1.83.7 or later to mitigate this SQL Injection vulnerability.
  • Implement input validation and sanitization for all user-provided data in API requests to prevent SQL injection.
  • Use prepared statements and parameterized queries to prevent unauthorized access via database queries.
  • Regularly update and review security configurations to align with best practices in database security.
  • Conduct regular security audits and dynamic testing to identify potential vulnerabilities in your system.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.