PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19 · 6h 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers · 16h F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE · 16h CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities · 17h Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required · 17h Java4Shell Flaw Threatens Global Enterprises, Java Application Ecosystem · 18h How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) · 20h Vulnerabilities in LMS software · 22h New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years · 22h AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor · 22h PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19 · 6h 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers · 16h F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE · 16h CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities · 17h Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required · 17h Java4Shell Flaw Threatens Global Enterprises, Java Application Ecosystem · 18h How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) · 20h Vulnerabilities in LMS software · 22h New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years · 22h AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor · 22h
🛡️
ACyber Sentinel Security Assessment Team
← Back to feed
⚠️ Vulnerability Report

CVE-2026-42208

CVE-2026-42208 - BerriAI LiteLLM SQL Injection Vulnerability - [Actively Exploited]

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.

Published: May 08, 2026 04:16

Last Modified: Jul 15, 2026 02:21