Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-42208 – Pre-auth SQL Injection in LiteLLM proxy allowing data theft and modification

Be the first to know when new zero-days emerge:

Summary

CVE-2026-42208 is a critical pre‑authentication SQL injection in the LiteLLM proxy (AI Gateway). The vulnerability exists in how the proxy constructs a database query used during API‑key verification: caller-supplied key data was incorporated directly into query text instead of being passed as a parameter. An attacker can reach this code path by sending a specially crafted Authorization header to any LLM API route (for example, POST /chat/completions) and trigger the proxy’s error handling to exercise the vulnerable query.

Affected software

  • Product: LiteLLM (proxy / AI gateway)
  • Versions: >= 1.81.16 and < 1.83.7
  • Patched in: 1.83.7 (vendor recommends upgrading to the latest stable release)

Severity

  • CVSS 3.1 Base Score: 9.8 (CRITICAL)
  • Attack Vector: Network
  • Privileges Required: None (pre‑auth)
  • User Interaction: None

Impact

  • Confidentiality: High — attackers can read sensitive data from the proxy database (including API keys and credentials managed by the proxy).
  • Integrity: High — evidence indicates an attacker may be able to modify database records, potentially changing credentials or authorization state.
  • Availability: High — database modification could also disrupt service.

Successful exploitation can lead to unauthorized access to the proxy, theft of managed credentials (API keys), and further compromise of dependent systems and services.

Observed activity and guidance

  • The issue has been added to the CISA Known Exploited Vulnerabilities catalog and an action due date was published (CISA guidance recommending mitigations/patching).
  • Security vendors and public reports indicated active exploitation shortly after disclosure; organizations should treat exposed LiteLLM proxies as high risk.

Mitigation and recommended actions

  • Immediate action: Upgrade LiteLLM to version 1.83.7 or later (or the vendor-recommended latest stable release).
  • If immediate upgrade is not possible:
    • Restrict network access to the proxy (limit to trusted IPs / internal network only).
    • Block or rate‑limit access to LLM API endpoints (e.g., POST /chat/completions) at perimeter controls or WAF.
    • Rotate any API keys and credentials managed by the proxy after patching.
    • Increase logging and monitoring for abnormal Authorization headers, unexpected DB errors, and unusual queries.
    • Apply WAF rules to detect and block SQL injection patterns targeting API key parameters.

References to review before/after patching

  • Review the vendor advisory and release notes for the exact patched versions and any additional mitigation guidance.
  • After patching, validate integrity of the proxy database and rotate credentials if compromise is suspected.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge