1-minute read of a 5 min report

LiteLLM Flaw Lets Read-Only Accounts Steal AI Gateway Secrets

By

1-minute read

What a defender needs to know

LiteLLM’s advisory says the /config/update authorization flaw is fixed in 1.83.0. Zenity observed file-read bodies matching CVE-2026-35029, reproduced the chain on 1.74.0, and says its test already returned HTTP 403 on 1.81.0; the available sources therefore do not establish 1.83.0 as the first build that rejected the bypass.

The file-read path sets UI_LOGO_PATH to a local secret file such as /app/.env or /proc/self/environ, then retrieves it through /get_image. Configuration writes can also replace UI_USERNAME and UI_PASSWORD or resolve os.environ/ references into outbound requests. The probes do not establish legitimate viewer access or a successful production compromise.

Upgrade to LiteLLM 1.83.9 or later for Check Point Research’s CVE-2026-59823 finding; LiteLLM lists 1.83.0 for /config/update. Require a strong unique master key and keep the Admin UI and management API off the public internet. Hunt for /config/update bodies that assign UI_LOGO_PATH to absolute paths, then correlate them with /get_image. Search for the example key sk-admin; the variables LITELLM_MASTER_KEY, DATABASE_URL, and OPENAI_API_KEY; /key/info, /key/list, /global/spend, /team/info, /user/info, /scim/v2/ServiceProviderConfig, and /scim/v2/Groups/1; the account [email protected]; and prototype-pollution probes with true admin/isAdmin under __proto__, or true admin under nested constructor/prototype (inert against LiteLLM’s Python proxy).

If that sequence succeeded, preserve request bodies, response codes and configuration history before containment. Rotate every model-provider, database, cloud and monitoring secret the proxy could resolve, and inspect newly created users, keys and outbound routes.

Test a viewer account after upgrading. /config/update must deny the request, and UI_LOGO_PATH, UI_USERNAME, and UI_PASSWORD must remain unchanged. The expected result is no viewer-level configuration write and no route that returns a local secret file.

Primary sources