CVE-2026-114612 BerriAI CVE debrief

Who should care

Defenders responsible for LiteLLM deployments, particularly those using versions 1.87.0 through 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0-rc.2, should assess exposure and prioritize verification and upgrades to fixed versions.

Why it matters

CVE-2026-114612 is a critical vulnerability in LiteLLM that allows authenticated internal users to gain administrative access and execute arbitrary commands. Defenders should prioritize verifying and upgrading to fixed versions, assessing exposure in their environments, and monitoring for potential exploitation attempts.

• Potential for authenticated internal users to gain administrative access
• Possible execution of arbitrary commands through the MCP stdio endpoint
• Need for verification of LiteLLM versions and upgrades to fixed versions
• Importance of monitoring for potential exploitation attempts

Technical summary

LiteLLM, a proxy server for LLM APIs, has a vulnerability in versions 1.87.0 through 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0-rc.2. The vulnerability allows an authenticated internal user to craft metadata containing a forged administrator credential, which can be replayed as a bearer token to gain administrative access and execute arbitrary commands through the MCP stdio endpoint. This issue arises from the proxy reusing one cryptographic context for at-rest secrets and session tokens. Defenders should prioritize verifying and upgrading to fixed versions of LiteLLM, specifically 1.100.4, 1.101.3, 1.102.2, 1.103.1, or 1.104.0-rc.2, and assess exposure in their environments.

Defensive priority

Defenders should prioritize verifying and upgrading to fixed versions of LiteLLM, specifically 1.100.4, 1.101.3, 1.102.2, 1.103.1, or 1.104.0-rc.2, and assess exposure in their environments.

Recommended defensive actions

• Verify and upgrade to fixed versions of LiteLLM (1.100.4, 1.101.3, 1.102.2, 1.103.1, or 1.104.0-rc.2)
• Assess exposure in environments using affected versions of LiteLLM
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability in LiteLLM, including affected versions and fixed versions. However, there is limited information on potential exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.