# CVE-2026-93355: LiteLLM Weak JWT Authentication via Email-Based User Lookup

> Attackers can impersonate any user and gain admin privileges by exploiting unverified email claims in JWT authentication, leading to unauthorized access to API keys and user management.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-g83g-3c4g-cfm5, MINI-26rm-gjvm-c352, MINI-39w7-pm94-64hm, MINI-442h-284g-gccj, MINI-5vhj-w45m-p7gp, MINI-5vxj-9vxx-4p6v, MINI-7283-48j3-7gqq, MINI-gmcj-27q7-m8xv, MINI-h3fj-rr29-jg99, MINI-q3h4-9v7f-pw74, MINI-v49x-pc3g-4vh5, MINI-v8qr-mp6x-x4jr, MINI-w2mp-9c29-mj7g, MINI-xwgm-whvj-xpx8

## What is CVE-2026-93355?

CVE-2026-93355 is a high-severity authentication bypass vulnerability in BerriAI litellm, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LiteLLM contains a weak authentication vulnerability that allows an attacker holding a valid JWT from the configured identity provider to authenticate as any existing user by exploiting an email-based fallback lookup in the JWT authentication flow without verifying the email_verified claim. Attackers can present a token with an unverified email address matching a victim's account to inherit the victim's role, including proxy_admin privileges, and permanently overwrite the victim's stored identity binding to retain persistent unauthorized access to administrative endpoints exposing API keys and user management.

Weakness: CWE-1390 (Weak Authentication)

## Which versions are affected by CVE-2026-93355?


## How do I fix CVE-2026-93355?

Apply the vendor's patch.

## Is CVE-2026-93355 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93355 exists.

Public exploit code:

- Benign, offline reproduction of CVE-2026-93355 — LiteLLM unverified-email JWT account takeover (runs LiteLLM's real code) (github_poc): https://github.com/InertFluid/cve-2026-93355-lab

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93355 and fix it if it is affected.

What it is: CVE-2026-93355 is a high-severity authentication bypass vulnerability in BerriAI litellm, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93355 exists.

Affected product: BerriAI litellm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93355/ (Markdown: https://insights.sbomify.com/CVE-2026-93355/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93355
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93355
- OSV: https://osv.dev/vulnerability/CVE-2026-93355

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93355/
Summaries are generated and may contain mistakes; the official description above is the record.