# GHSA-g5ff-637f-6q2m: LiteLLM: internal_user_viewer arbitrary local file read via `vertex_ai_credentials`


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Oct 2026

## What is GHSA-g5ff-637f-6q2m?

GHSA-g5ff-637f-6q2m is a vulnerability in litellm, published on 27 Oct 2026. 

### Official description

## Summary

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.

## Impact

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.

## Remediation

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.

## Which versions are affected by GHSA-g5ff-637f-6q2m?

2 open source packages ship an affected version, including litellm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `litellm` | PyPI | All versions | 1.95.0 |
| `litellm` | PyPI | All versions | 1.95.0 |

## How do I fix GHSA-g5ff-637f-6q2m?

Upgrade litellm to 1.95.0 or later.

## Is GHSA-g5ff-637f-6q2m being exploited?

There is no known exploitation of GHSA-g5ff-637f-6q2m in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g5ff-637f-6q2m and fix it if it is affected.

What it is: GHSA-g5ff-637f-6q2m is a vulnerability in litellm, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of GHSA-g5ff-637f-6q2m in the wild and no public exploit code.

Affected packages and fixed versions:
- litellm (PyPI): affected all versions; fixed in 1.95.0
- litellm (PyPI): affected all versions; fixed in 1.95.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-g5ff-637f-6q2m/ (Markdown: https://insights.sbomify.com/GHSA-g5ff-637f-6q2m/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g5ff-637f-6q2m

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g5ff-637f-6q2m/
Summaries are generated and may contain mistakes; the official description above is the record.