CVE-2026-35029
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLiteLLM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLiteLLM versions before 1.83.0 have an IDOR/authorization bypass on the /config/update endpoint that fails to enforce admin role checks. Authenticated users can modify proxy configuration, environment variables, and register malicious pass-through endpoint handlers pointing to attacker-controlled Python code for RCE. They can also read arbitrary server files via UI_LOGO_PATH and /get_image, and hijack other accounts by overwriting UI_USERNAME and UI_PASSWORD environment variables.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.83.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check LiteLLM versionRun 'pip show litellm' or check your package manager to identify the installed LiteLLM versionAffected if The installed version is any version before 1.83.0 (e.g., 1.82.0, 1.80.0, etc.)
-
Verify admin role enforcement on /config/updateAttempt a limited test of the /config/update endpoint with a non-admin authenticated user account, observing whether the request succeeds without returning a 403 Forbidden errorAffected if Non-admin users can successfully modify proxy configuration, environment variables, or register handlers through this endpoint
-
Inspect UI_LOGO_PATH configurationReview LiteLLM configuration files or environment variables for the UI_LOGO_PATH setting, checking if it allows arbitrary file path specificationAffected if UI_LOGO_PATH can be set to any file system path, enabling arbitrary file read access
-
Audit user account configurationExamine stored user credentials (UI_USERNAME/UI_PASSWORD) in your configuration and verify that admin accounts have not been modified or hijacked by reviewing user role assignmentsAffected if Admin accounts have been modified, new accounts have been added with elevated privileges, or credentials have been changed without your knowledge
Your environment is affected if LiteLLM version is below 1.83.0 and the /config/update endpoint is accessible to non-admin authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.83.0
Upgrade LiteLLM to v1.83.0 or later which enforces admin role authorization on the /config/update endpoint.
1.83.0
- Identify the current LiteLLM version currently deployed in your environment
- Upgrade LiteLLM to version 1.83.0 or later by updating the package or container image
- Verify the upgrade was successful by checking the installed version matches or exceeds 1.83.0
- Confirm that the /config/update endpoint now properly enforces admin role authorization before allowing configuration changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35029 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data