litellm: Incorrect Authorization
CVE-2026-35029 is a high-severity incorrect authorization vulnerability in litellm from BerriAI, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected litellm versions: < 1.83.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 38.6% chance of exploitation within 30 days, which is in the top 1.4% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Check which version of litellm you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| BerriAI | litellm | < 1.83.0 | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.6 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI 2.25 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI 3.3 | Not specified in the record | Not stated |
| Red Hat | Lightspeed Core | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI (RHOAI) | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (github.com) |
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CNA |
Official description
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, the /config/update endpoint does not enforce admin role authorization. A user who is already authenticated into the platform can then use this endpoint to modify proxy configuration and environment variables, register custom pass-through endpoint handlers pointing to attacker-controlled Python code, achieving remote code execution, read arbitrary server files by setting UI_LOGO_PATH and fetching via /get_image, and take over other privileged accounts by overwriting UI_USERNAME and UI_PASSWORD environment variables. Fixed in v1.83.0.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- seclists.org/fulldisclosure/2026/Apr/17
- access.redhat.com/errata/RHSA-2026:13545
- access.redhat.com/errata/RHSA-2026:28960
- access.redhat.com/errata/RHSA-2026:30056
- access.redhat.com/security/cve/CVE-2026-35029
- bugzilla.redhat.com/show_bug.cgi?id=2455474
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35029.json
Other vulnerabilities in litellm
- 9.9 Critical severity
- 8.1 High severity
- 7.7 High severity
- 8.2 High severity
BerriAI LiteLLM Improper Authentication Exploited
- 7.2 High severity
- 9.8 Critical severity
Recent Incorrect Authorization vulnerabilities
- 8.1 High severity
- 8.8 High severity
- 9.1 Critical severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.