Check Point Research: When LLM Gateways Go Wrong, findings from LiteLLM

Evidence record

Original Oct 13 investigation: CVE-2026-35029 and CVE-2026-59823, configuration authorization and nested routing.

Read the original source ↗

Claim-level citations (4)

• supportsLiteLLM proxy configuration update let lower-privileged users reach admin effects: The configuration path was used in controlled demonstrations of local file reads, administrative takeover and execution through malicious imported Python modules.

  PoC impact examples and cloud-storage Python module path

• supportsLiteLLM proxy configuration update let lower-privileged users reach admin effects: Check Point reproduced low-privilege configuration updates through /config/update due to missing proxy-admin authorization.

  CVE-2026-35029, missing authorization for /config/update

• supportsLiteLLM nested routing field could send provider credentials to a foreign destination: Check Point documented nested user_config.api_base bypass of top-level route validation, letting an authenticated user redirect provider outbound calls.

  CVE-2026-59823, nested user_config parameter and router construction

• supportsLiteLLM nested routing field could send provider credentials to a foreign destination: The controlled test showed provider credentials could accompany misdirected requests; the issue was fixed in LiteLLM 1.83.9.

  CVE-2026-59823 exploit and version remediation