LiteLLM / LiteLLM

LiteLLM Proxy Authentication Failed — 'failed-to-connect-to-db' Bypass Vulnerability (CVE-2026-42208)

Understand and mitigate LiteLLM Proxy auth bypass via SQL injection where DB connection errors grant PROXY_ADMIN privileges without valid keys Includes evidence for LiteLLM troubleshooting demand.

Source-backed Last updated June 3, 2026 4 sources Needs local verification

Category: LiteLLM
Error signature: Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: June 3, 2026
Verification status: Source-backed
Evidence: 4 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for LiteLLM, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error is a LiteLLM failure pattern reported for developers trying to understand and mitigate litellm proxy auth bypass via sql injection where db connection errors grant proxy_admin privileges without valid keys. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

CVE-2026-42208: Pre-auth SQL injection in LiteLLM Proxy's key verification path. When PrismaDB returns any PrismaError, auth_exception_handler grants PROXY_ADMIN access with key='failed-to-connect-to-db'. Actively exploited in the wild. Developer-facing: teams running LiteLLM Proxy need to understand auth failure modes and upgrade immediately. Active exploitation evidence discovered 36 hours post-disclosure. Category: LiteLLM per approved list.

Common causes

CVE-2026-42208: Pre-auth SQL injection in LiteLLM Proxy's key verification path. When PrismaDB returns any PrismaError, auth_exception_handler grants PROXY_ADMIN access with key='failed-to-connect-to-db'. Actively exploited in the wild. Developer-facing: teams running LiteLLM Proxy need to understand auth failure modes and upgrade immediately. Active exploitation evidence discovered 36 hours post-disclosure. Category: LiteLLM per approved list.

Quick fixes

Confirm the exact error signature matches Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error.
Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error exactly before applying the quick fix.
Compare the failing environment with LiteLLM versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error mean in LiteLLM?

Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error indicates the workflow described by "LiteLLM Proxy Authentication Failed — 'failed-to-connect-to-db' Bypass Vulnerability (CVE-2026-42208)" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error?

Check whether this cause matches your environment: CVE-2026-42208: Pre-auth SQL injection in LiteLLM Proxy's key verification path. When PrismaDB returns any PrismaError, auth_exception_handler grants PROXY_ADMIN access with key='failed-to-connect-to-db'. Actively exploited in the wild. Developer-facing: teams running LiteLLM Proxy need to understand auth failure modes and upgrade immediately. Active exploitation evidence discovered 36 hours post-disclosure. Category: LiteLLM per approved list.

Is the Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error guidance source-backed?

The "LiteLLM Proxy Authentication Failed — 'failed-to-connect-to-db' Bypass Vulnerability (CVE-2026-42208)" page is labeled source-backed. It has 4 public source URLs from docs.litellm.ai, bishopfox.com, sysdig.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error?

For "LiteLLM Proxy Authentication Failed — 'failed-to-connect-to-db' Bypass Vulnerability (CVE-2026-42208)", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Authentication failed / failed-to-connect-to-db / PrismaError pool timeout connection error?

For "LiteLLM Proxy Authentication Failed — 'failed-to-connect-to-db' Bypass Vulnerability (CVE-2026-42208)", collect the failing LiteLLM command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.