Tia N.List

Reported by 3 outlets

LiteLLM Admin API Broken Authorization Exploited in the Wild

warm3.4
Why this score
Breadth
1.50 / 2.0 · 3 sources
Authority
1.20 / 2.0 · best outlet weight
Severity
1.40 / 5.0 · CVSS + content signals
Velocity
0.50 / 2.0 · updates in 48h
Pickup speed
0.52 / 0.6 · time to second source
Recency
× 0.67 temporal multiplier
Community
+ 0.00 / 1.5 · reddit signal
Score
3.4 / 10 = base × recency + community
cyberpress.orggbhackers.commalware.news CVE-2026-35029CVE-2026-59823 first seen 41d ago

Analysis

Hackers are exploiting a broken authorization flaw in LiteLLM's /config/update endpoint (CVE-2026-35029, CVE-2026-59823) to turn read-only access into full server takeover. The missing authorization check allows any authenticated user, including low-privileged accounts, to modify proxy runtime configuration, leading to arbitrary file read, admin takeover, and remote code execution via malicious Python modules. LiteLLM 1.83.9 resolves the issues.

Timeline

  1. original reporting

    Hackers Exploit LiteLLM Admin API Flaw to Turn Read-Only Access Into Full Server Takeover

    cyberpress.org · 41d ago · September 2nd, 2026

    A broken authorization check in LiteLLM’s administrative API is being actively targeted, allowing attackers with even read-only access to alter gateway settings, expose secrets, and seize administrator control. Zenity observed exploitation attempts against CVE-2026-35029, a broken-access-control vulnerability affecting LiteLLM’s /config/update endpoint. The flaw, disclosed on April 6, 2026 and fixed in LiteLLM version 1.83.0, enables accounts assigned the supposedly limited proxy_admin_viewer role to modify settings reserved for full administrators. Hackers Exploit LiteLLM Admin API Flaw That poses a severe risk to LiteLLM deployments, which commonly sit between applications and AI providers and handle model-provider API keys, user data, spending records, databases, and administrator credentials. Honeypot telemetry collected between February and June 2026 recorded roughly 3,900 requests targeting LiteLLM administrative APIs from 73 IP addresses. About 1,000 requests targeted /config/update , the route used by the LiteLLM dashboard to modify live proxy configuration. The first observed attempts arrived on April 7, one day after CVE-2026-35029 became public. More specific file-read payloads were observed from May 5 through May 12, indicating that attackers rapidly incorporated the vulnerability into their scanning and exploitation activities. The central issue is that /config/update did not properly verify whether the authenticated account had administrative privileges. A low-p

  2. update from gbhackers.com

    Hackers Exploit LiteLLM Admin API Flaw to Turn Read-Only Access Into Full Server Takeover

    gbhackers.com · 41d ago · September 2nd, 2026

    This vulnerability allows low-privileged, read-only users to modify proxy configurations, expose sensitive secrets, and potentially gain full administrator control over affected servers. Researchers at Zenity Labs tracked approximately 3,900 requests targeting LiteLLM’s administration endpoints from February to June 2026, originating from 73 different […] The post Hackers Exploit LiteLLM Admin API Flaw to Turn Read-Only Access Into Full Server Takeover appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform .

  3. update from malware.news

    When LLM Gateways Go Wrong: Findings from LiteLLM

    malware.news · 14h ago · October 13th, 2026

    TL;DR; Our security assessment of LiteLLM (v1.77.7), a widely used open-source LLM gateway, uncovered multiple high-impact vulnerabilities (tracked as CVE-2026-35029 , CVE-2026-59823) which have been resolved as of LiteLLM version 1.83.9. The most significant issues stemmed from a missing authorization check on the /config/update endpoint, which allowed any authenticated user (including low-privileged accounts) to modify the proxy’s runtime configuration. This single flaw enabled arbitrary file read, administrative account takeover, and remote code execution via malicious Python modules loaded from cloud storage. A separate SSRF vulnerability in the “Clientside LLM Credentials” feature allowed attackers to redirect API calls and exfiltrate provider keys. These findings highlight that as AI infrastructure tools rapidly evolve, foundational security practices like proper access control and input validation remain essential. Introduction As LLM gateways see wider adoption, understanding the security risks they introduce is essential to deploying them safely within an AI stack.

Source on GitHub