CVSS 4.0
9.4 criticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NCritical (9.4) in litellm litellm. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in litellm 1.83.0.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Nlitellm (PyPI): fixed in 1.83.0Explain CVE-2026-35030 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-35030?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-35030?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-35030 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| litellm:litellm | before 1.83.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-jjhc-v7c2-5hh6 | PyPI | litellm | <1.83.0 | 1.83.0 |
| PYSEC-2026-390 | PyPI | litellm | <1.83.0 | 1.83.0 |
Red Hat rates this Important.
This is an Important flaw in LiteLLM that enables authentication bypass and privilege escalation. The vulnerability is present only when JWT authentication is explicitly enabled, as this configuration is not active by default. Red Hat Ansible Automation Platform, Lightspeed Core, Red Hat OpenShift AI, and Ansible Services are affected if configured with JWT authentication.
To mitigate this issue, ensure that JWT authentication is not enabled in LiteLLM configurations. The vulnerability only manifests when `enable_jwt_auth` is set to `true`. If JWT authentication is not strictly required, disable it to prevent potential authentication bypass and privilege escalation. If this configuration is changed, a restart of the LiteLLM service may be required for the changes to take effect.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Ansible Automation Platform 2.6 | ansible-automation-platform-26/lightspeed-chatbot-rhel9:1777398576 | Fixed 2026-05-04 | RHSA-2026:13545 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-llama-stack-core-rhel9:1781826406 | Fixed 2026-06-24 | RHSA-2026:28960 |
| Red Hat OpenShift AI 3.3 | rhoai/odh-llama-stack-core-rhel9:1782310008 | Fixed 2026-06-25 | RHSA-2026:30056 |
| Lightspeed Core | redhat-user-workloads/lightspeed-stack | Affected | |
| Red Hat Ansible Automation Platform 2 | redhat-user-workloads/lightspeed-chatbot-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-mlflow-rhel9 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-35030.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.