<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cve-2026-42208 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-42208/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 29 Apr 2026 15:21:58 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-42208/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>LiteLLM Pre-Auth SQL Injection Vulnerability (CVE-2026-42208)</title><link>https://feed.craftedsignal.io/briefs/2026-04-litellm-sqli/</link><pubDate>Wed, 29 Apr 2026 15:21:58 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-litellm-sqli/</guid><description>A critical pre-authentication SQL injection vulnerability (CVE-2026-42208) in LiteLLM allows an unauthenticated remote attacker to extract all stored API keys and provider credentials, potentially leading to a complete compromise of connected AI provider accounts; active exploitation is reported, and the vulnerability is fixed in version v1.83.7.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>LiteLLM is an AI gateway that centralizes API credentials for various providers like OpenAI and Anthropic. A pre-authentication SQL injection vulnerability, identified as CVE-2026-42208, allows an unauthenticated remote attacker to extract all stored API keys and provider credentials. Successful exploitation is equivalent to compromising all connected AI provider accounts. Open-source intelligence suggests active exploitation attempts in the wild. The vulnerability stems from directly concatenating the Bearer token value from incoming HTTP requests into a SQL query without proper sanitization before authentication. This allows for arbitrary SQL injection. The issue is resolved in LiteLLM version v1.83.7. Defenders should prioritize patching or mitigating this vulnerability immediately due to the high risk of credential compromise.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker sends a malicious HTTP request to the LiteLLM server.</li>
<li>The HTTP request contains a crafted <code>Authorization: Bearer</code> header.</li>
<li>The <code>Bearer</code> token value contains a SQL injection payload.</li>
<li>LiteLLM's authentication mechanism directly concatenates the <code>Bearer</code> token into a SQL query without sanitization.</li>
<li>The injected SQL code executes within the LiteLLM database.</li>
<li>The injected SQL is designed to extract API keys and provider credentials stored in the database.</li>
<li>The extracted credentials are returned to the attacker within the HTTP response, or via an out-of-band channel configured in the injected SQL.</li>
<li>The attacker uses the stolen API keys and credentials to access and control the victim's AI provider accounts.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to steal all API keys and credentials managed by the LiteLLM instance. This is equivalent to losing control over all connected AI provider accounts, including those for OpenAI and Anthropic. This may lead to unauthorized usage of AI services, data breaches, and other malicious activities. Open-source reporting indicates active exploitation, suggesting a high risk of widespread impact.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately patch LiteLLM instances to version v1.83.7 to remediate CVE-2026-42208.</li>
<li>If patching is not immediately feasible, configure <code>&quot;set disable_error_logs: true&quot;</code> under general settings in LiteLLM to mitigate the vulnerability, as recommended by CCB.</li>
<li>Deploy the Sigma rule <code>Detect Suspicious LiteLLM Authentication Header</code> to identify potential exploitation attempts by monitoring for suspicious patterns in the <code>Authorization</code> header of HTTP requests to the LiteLLM server.</li>
<li>Upscale monitoring and detection capabilities, as recommended by CCB, to identify any related suspicious activity and ensure a swift response in case of an intrusion.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">threat</category><category>sql-injection</category><category>credential-theft</category><category>cve-2026-42208</category></item></channel></rss>