GHSA-G5FF-637F-6Q2M

LiteLLM: internaluserviewer arbitrary local file read via vertexaicredentials

An authenticated LiteLLM proxy user could read arbitrary local files from the proxy runtime by sending a crafted vertex_ai_credentials value to /utils/transform_request. The request-body safety blocklist rejected vertex_credentials but missed its alias vertex_ai_credentials, which let the value reach the Vertex AI credential loader and trigger a file read that is sent to an attacker-controlled URL.

A low-privilege authenticated user (only internal_user_viewer, obtainable through SSO login on many deployments) could read any file readable by the LiteLLM process. Reading files such as /proc/self/environ can disclose LITELLM_MASTER_KEY and provider API keys, so the impact can escalate to full proxy-admin control.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

GHSA-G5FF-637F-6Q2M has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.95.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Upgrade to 1.95.0 or later. The fix adds the missing alias to the request-body blocklist, so no configuration change is needed once you upgrade. There is no reliable configuration workaround on affected versions.

1. What is GHSA-G5FF-637F-6Q2M? GHSA-G5FF-637F-6Q2M is a high-severity improper input validation vulnerability in litellm (pip), affecting versions < 1.95.0. It is fixed in 1.95.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is GHSA-G5FF-637F-6Q2M? GHSA-G5FF-637F-6Q2M has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of litellm are affected by GHSA-G5FF-637F-6Q2M? litellm (pip) versions < 1.95.0 is affected.
4. Is there a fix for GHSA-G5FF-637F-6Q2M? Yes. GHSA-G5FF-637F-6Q2M is fixed in 1.95.0. Upgrade to this version or later.
5. Is GHSA-G5FF-637F-6Q2M exploitable, and should I be worried? Whether GHSA-G5FF-637F-6Q2M is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-G5FF-637F-6Q2M is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-G5FF-637F-6Q2M? Upgrade litellm to 1.95.0 or later.

Other vulnerabilities in litellm