CVE-2026-42208
Consistent multi-source reports of active exploitation, rapid weaponization timeline, and defender patch calls. KEV absence and missing NVD metadata reduce confidence slightly.
What: SQL injection in LiteLLM proxy (AI gateway) allowing unauthenticated database access to API keys for OpenAI, Anthropic, AWS and other upstream providers. CVSS/EPSS scores unavailable.
Why it matters: Social chatter consistently reports in-the-wild exploitation within 36 hours of public disclosure. Posts describe active weaponization targeting credential vaults in production AI infrastructure. Multiple security vendors and analysts flagging urgent patch requirement. No KEV listing evident in metadata, but defender urgency and rapid exploitation timeline are strong signals of real compromise activity.
Where it's seen: X and Bluesky posts from security researchers, vendor advisories, and threat intelligence accounts repeating near-identical "36 hours to exploitation" narrative. Framing emphasizes AI supply-chain risk and credential exposure severity.
RISK: CRITICAL — Unauthenticated SQL injection in widely-deployed AI proxy exfiltrating upstream API keys to production systems.
Public PoCs on GitHub 6 repos
- nomi-sec/PoC-in-GitHub ★ 7687
📡 PoC auto collect from GitHub. ⚠️ Be careful Malware.
- DarkFunct/TK-CVE-Repo ★ 49 · Python
TK-CVE-Repo
- ScottyxNova/QMasters-TIA ★ 1 · Shell
- imjdl/CVE-2026-42208_lab ★ 0 · Python
CVE-2026-42208 lab
- AryaVeerJai/cybersecurity-news-updater ★ 0
Automated GitHub Actions workflow that fetches and updates the latest cybersecurity news every Tuesday and Thursday using RSS feeds.
Articles & coverage 15 articles
- Critical LiteLLM SQL Injection Vulnerability Exploited in the Wild
# Critical LiteLLM SQL Injection Vulnerability Exploited in the Wild. A critical pre-authentication SQL injection vulnerability, tracked as CVE-2026-42208, has been discovered in the widely used LiteLLM gateway, exposing sensitive backend databases to unauthorized access. Security researchers have confirmed that threat actors are already actively exploiting this flaw to steal high-value secrets, i
- CVE-2026-42208
Vulmon Logo Vulmon Recent Vulnerabilities Research Posts Trends Blog Docs About Contact. # CVE-2026-42208. ## Vulnerability Summary. Hackers are exploiting a critical LiteLLM pre-auth SQLi flaw By Bill Toulas April 28, 2026 05:07 PM 0 Hackers are targeting sensitive information stored in the LiteLLM open-source large-language model (LLM) gateway by exploiting a critical vulnerability tracked as
- vLiteLLM CVE-2026-42208 SQL Injection Exploited
**CVE-2026-42208** shows how quickly attackers now move against vulnerable AI infrastructure. The critical **SQL Injection** flaw in BerriAI’s **LiteLLM** Python package was exploited in the wild within about 36 hours of advisory publication. That means attackers moved before many DevOps teams, cloud security teams, and AI platform operators could even finish triage. Attackers targeted LiteLLM’s p
- CVE-2026-42208: LiteLLM bug exploited 36 hours after its disclosure
## Attackers quickly exploited a critical LiteLLM flaw (CVE-2026-42208) to access and modify sensitive database data via SQL injection. The vulnerability, an SQL injection in the proxy API key verification process, lets attackers access and potentially modify database data. An unauthenticated attacker could send a specially crafted `Authorization` header to any LLM API route (for example `POST /ch
- LiteLLM exploited within 36 hours of disclosure via SQL injection bug
For the second time in five weeks, BerriAI’s LiteLLM Python package was exploited in the wild, this time within 36 hours of disclosure.In the latest exploit, a critical SQL injection bug — CVE-2026-42208 — could let an attacker read data from the proxy’s database and modify it, leading to unauthorized access to the proxy and the credential it manages.The maintainers said if it’s not possible to im
Top posts driving the trend
@EnigmaGlobalSWX · 5/3/2026Intel Report [CRITICAL] - A critical pre-authentication SQL injection vulnerability (CVE-2026-42208, CVSS 9.3) in LiteLLM, a widely-used open-source AI gateway with over 22,000 GitHub stars, was actively exploited within 36 hours and 7 minutes of its... https://t.co/wAJGkjzZTx
♥ 0 · ↻ 0 · 💬 0- @technoholic.bsky.socialBluesky · 5/2/2026
Critical flaw CVE-2026-42208 (CVSS 9.3) in BerriAI's LiteLLM was exploited in the wild just 36 hours after disclosure. It's an SQL injection risk enabling data modification. Stay alert!
♥ 0 · ↻ 0 · 💬 0
@technoholic_meX · 5/2/2026Critical flaw CVE-2026-42208 (CVSS 9.3) in BerriAI's LiteLLM was exploited in the wild just 36 hours after disclosure. It's an SQL injection risk enabling data modification. Stay alert! https://t.co/xEbMwBkO0N
♥ 0 · ↻ 0 · 💬 0- BL@blumirasecX · 5/1/2026
The threat landscape didn't slow down this week — and we've got everything you need to know: 🔴 CISA flagged two more actively exploited vulnerabilities. 🔴 A SQL injection flaw in LiteLLM (CVE-2026-42208) is being weaponized in the wild. 🔴 ShinyHunters worked their way into https://t.co/PBXye5zt5D
♥ 0 · ↻ 0 · 💬 0 - T_@t_dharmX · 5/1/2026
3 AI tools exploited in 36hrs this quarter! LiteLLM CVE-2026-42208: advisory to SQLi in 36h7m. Reaches OpenAI + Anthropic + AWS keys in ONE Postgres row. Your AI gateway = credential vault. No audit category yet. Fix this now!
♥ 1 · ↻ 1 · 💬 1 - @concisecyber.bsky.socialBluesky · 5/1/2026
LiteLLM CVE-2026-42208 SQL Injection Exploited Within 36 Hours of Disclosure LiteLLM CVE-2026-42208, a critical SQL injection flaw, was exploited in the wild within 36 hours of disclosure. Patch now.
♥ 0 · ↻ 0 · 💬 0 - @awesomeagents.bsky.socialBluesky · 5/1/2026
LiteLLM Exploited 36 Hours After Vulnerability Disclosure https://awesomeagents.ai/news/litellm-sql-injection-cve-2026-42208/ #Security #Cybersecurity #DeveloperTools
♥ 0 · ↻ 0 · 💬 0 - AW@awagentsX · 5/1/2026
Attackers hit CVE-2026-42208, a critical pre-auth SQL injection in LiteLLM proxy, within 36 hours of the public advisory - targeting database tables holding API keys for every upstream AI provider. #Security #Cybersecurity Link in the first comment 👇 https://t.co/UJFIKQ5Z0R
♥ 0 · ↻ 0 · 💬 1 - TH@TheCyberSecHubX · 5/1/2026
CVE-2026-42208: LiteLLM bug exploited 36 hours after its disclosure https://t.co/iBJWlgEixj #ArtificialIntelligence #BreakingNews #Hacking #Security
♥ 2 · ↻ 0 · 💬 0 - JN@JNitterauerX · 5/1/2026
🤖 AI security risk: CVE-2026-42208 SQL injection in LiteLLM actively exploited. Your AI gateway could be leaking every LLM API key you own. Patch or take offline NOW. https://t.co/mUcmSl48Kq #AISecurity #cybersecurity #LiteLLM
♥ 0 · ↻ 0 · 💬 0 - TH@TheCyberDefX · 5/1/2026
CVE-2026-42208: Critical LiteLLM SQL Injection Exploited in Wild https://t.co/eN4PqXiJzE #CVE202642208 #LiteLLMSQL #Cybersecurity
♥ 0 · ↻ 0 · 💬 0 - TA@tatha_gautamaX · 5/1/2026
• #Hacked #Malware #Spyware #Zerodays #Ransomware #Phishing #Backdoor #RCE #RAT ☠️ • • #CyberSecurity #CyberCrime #DataHack #DataPrivacy #DataTheft #DataLeaks #DataBreach 💾 • » LiteLLM CVE-2026-42208 SQL Injection Exploited within 36 Hours of Disclosure
♥ 0 · ↻ 0 · 💬 0 - MY@MyDooM15X · 5/1/2026
📡 Observed: LiteLLM CVE-2026-42208 SQL Injection Exploited within 36 Hours of Disclosure https://t.co/58QMbL2mZ7 #MachineLearning #AI #Privacy
♥ 0 · ↻ 0 · 💬 0