High‑Severity SQL Injection in BerriAI LiteLLM (CVE‑2026‑42208) Threatens Credential Stores
What It Is
BerriAI LiteLLM contains an unchecked SQL query that can be manipulated by an attacker to inject arbitrary SQL commands. The flaw permits reading from, and potentially altering, the proxy’s underlying database, which stores the credentials that the service manages on behalf of its users.
Exploitability
The vulnerability is publicly disclosed in the CISA Known Exploited Vulnerabilities (KEV) catalog and assigned a High severity rating. No confirmed active exploitation has been reported, but a proof‑of‑concept exists in the public advisory, indicating that a skilled adversary could weaponize the flaw with relatively low effort.
Affected Products
- Vendor: BerriAI
- Product: LiteLLM (AI/ML inference proxy)
Why It Matters for Compliance & Audit Readiness
- Access Controls: The ability to read or modify the credential store directly undermines logical access controls and segregation of duties.
- Vendor‑Management Controls: Organizations that have delegated credential handling to LiteLLM must demonstrate due‑diligence in monitoring third‑party risk.
- Continuous Control Monitoring: Detecting anomalous database queries or unauthorized proxy access is essential for maintaining a defensible audit trail under frameworks such as NIST CSF, ISO 27001, and SOC 2.
- Evidence of Remediation: Prompt patching, log‑review, and credential rotation provide concrete evidence of control effectiveness for auditors.
Recommended Actions
- Patch Management: Apply the vendor‑released fix for CVE‑2026‑42208 immediately.
- Inventory & Scope: Identify all instances of LiteLLM in your environment and map them to the affected control (access‑control/credential‑management).
- Log Review & Monitoring: Enable detailed query logging on the LiteLLM proxy database; set alerts for unexpected SELECT/UPDATE statements.
- Credential Rotation: Rotate all credentials stored in the LiteLLM proxy after patching, and verify that no unauthorized changes were made.
- Vendor Risk Update: Document the vulnerability in your vendor‑risk register, update the risk assessment, and capture remediation evidence for audit purposes.
- Control Evidence Capture: Archive patch deployment logs, updated configuration baselines, and post‑remediation credential inventories as part of your continuous assurance program.
Source: https://nvd.nist.gov/vuln/detail/CVE-2026-42208