CVE-2026-35029

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 26.4%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 25%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
25%
EPSS %ILE
98%
KEV
Not listed

Published

April 6, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Apr 29, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic🟡 PoC Available

Full Disclosure: SEC Consult SA-20260421-0 :: Broken Access Control in Config Endpoint in LiteLLM

http://seclists.org/fulldisclosure/2026/Apr/17
github Patch Available

Privilege escalation via unrestricted proxy configuration endpoint · Advisory · BerriAI/litellm · GitHub

Affected: v1.83.0. The endpoint now requires

https://github.com/BerriAI/litellm/security/advisories/GHSA-53mr-6c8q-9789

Vendor Advisories for CVE-2026-35029(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17823100082026-06-25redhat
redhatrhoai/odh-llama-stack-core-rhel9:17818264062026-06-24redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17773985762026-05-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
litellm0.1.0 ... 1.9.dev0 (1101 versions)1.83.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-02 09:44 UTCOSV refresh
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 08:24 UTCEG score recompute
Show 75 more
  1. 2026-08-16 08:24 UTCVendor advisory
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 18:46 UTCVendor advisory
  5. 2026-08-14 05:32 UTCEG score recompute
  6. 2026-08-14 05:32 UTCVendor advisory
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 09:44 UTCVendor advisory
  9. 2026-08-12 19:45 UTCEG score recompute
  10. 2026-08-12 19:45 UTCVendor advisory
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-11 19:56 UTCEG score recompute
  13. 2026-08-11 19:56 UTCVendor advisory
  14. 2026-08-11 03:18 UTCVendor advisory
  15. 2026-08-10 07:12 UTCVendor advisory
  16. 2026-08-09 18:07 UTCVendor advisory
  17. 2026-08-09 05:02 UTCEG score recompute
  18. 2026-08-09 05:02 UTCVendor advisory
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-08 04:11 UTCEG score recompute
  21. 2026-08-08 04:11 UTCVendor advisory
  22. 2026-08-07 15:07 UTCEG score recompute
  23. 2026-08-07 15:07 UTCVendor advisory
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 13:13 UTCVendor advisory
  26. 2026-08-06 00:07 UTCEG score recompute
  27. 2026-08-06 00:07 UTCVendor advisory
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:38 UTCEPSS rescore
  31. 2026-08-03 22:28 UTCEG score recompute
  32. 2026-08-03 22:28 UTCVendor advisory
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 14:24 UTCEG score recompute
  35. 2026-08-02 14:24 UTCVendor advisory
  36. 2026-08-02 02:27 UTCEPSS rescore
  37. 2026-08-01 04:16 UTCEPSS rescore
  38. 2026-07-30 16:28 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-25 14:18 UTCEPSS rescore
  43. 2026-07-25 14:18 UTCEPSS rescore
  44. 2026-07-24 14:17 UTCEPSS rescore
  45. 2026-07-24 14:17 UTCEPSS rescore
  46. 2026-07-23 14:18 UTCEPSS rescore
  47. 2026-07-23 14:18 UTCEPSS rescore
  48. 2026-07-23 03:10 UTCEG score recompute
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-21 15:24 UTCEPSS rescore
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 02:29 UTCEPSS rescore
  53. 2026-07-18 10:04 UTCEPSS rescore
  54. 2026-07-17 02:24 UTCOSV refresh
  55. 2026-07-16 17:03 UTCEPSS rescore
  56. 2026-07-15 16:57 UTCEPSS rescore
  57. 2026-07-15 16:57 UTCEPSS rescore
  58. 2026-07-15 02:00 UTCEPSS rescore
  59. 2026-07-13 22:30 UTCEPSS rescore
  60. 2026-07-12 05:46 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 19:10 UTCEPSS rescore
  63. 2026-07-08 15:15 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-04 06:31 UTCEPSS rescore
  67. 2026-07-01 15:06 UTCEPSS rescore
  68. 2026-06-30 23:22 UTCEPSS rescore
  69. 2026-06-29 14:06 UTCEPSS rescore
  70. 2026-06-29 14:06 UTCEPSS rescore
  71. 2026-06-28 04:56 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-27 03:08 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-35029.yaml
    First seen Jan 1, 2026

    LiteLLM - Arbitrary File Read

    Open source ↗

Frequently asked(5)

What is CVE-2026-35029?
CVE-2026-35029 is a high vulnerability published on April 6, 2026. 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…
When was CVE-2026-35029 disclosed?
CVE-2026-35029 was first published in the National Vulnerability Database on April 6, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35029 actively exploited?
CVE-2026-35029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25% probability of exploitation in the next 30 days, which ranks it in the top 2.2% of all scored CVEs.
What is the CVSS score of CVE-2026-35029?
CVE-2026-35029 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-35029?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35029, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35029

Explore →

Is Your Infrastructure Affected by CVE-2026-35029?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs