# GHSA-hhww-mrg2-969h: LiteLLM vulnerable to reflected XSS in /sso/debug/callback


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

## What is GHSA-hhww-mrg2-969h?

GHSA-hhww-mrg2-969h is a vulnerability in litellm, published on 27 Oct 2026. 

### Official description

### Summary

The `/sso/debug/callback` endpoint reflected identity-provider-controlled fields into an inline `<script>` block via `json.dumps`, which escapes JSON string syntax but not HTML context characters such as `</script>`. An IdP-returned string field containing `</script>` (for example a user-editable display name) closed the script block and executed attacker JavaScript in the proxy's origin.

### Impact

Reflected XSS on the LiteLLM proxy origin. The route required no authentication, so an attacker with an account on the configured IdP whose claims pass such strings through verbatim could complete the SSO flow themselves and deliver the resulting callback URL to a logged-in proxy admin. Scripts executing in the proxy origin can read the dashboard session cookie and act with the victim's privileges, up to full admin account takeover.

## Which versions are affected by GHSA-hhww-mrg2-969h?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `litellm` | PyPI | From 1.65.5 | 1.85.0 |
| `litellm` | PyPI | From 1.65.5 | 1.85.0 |

## How do I fix GHSA-hhww-mrg2-969h?

Upgrade litellm to 1.85.0 or later.

## Is GHSA-hhww-mrg2-969h being exploited?

There is no known exploitation of GHSA-hhww-mrg2-969h in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hhww-mrg2-969h and fix it if it is affected.

What it is: GHSA-hhww-mrg2-969h is a vulnerability in litellm, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of GHSA-hhww-mrg2-969h in the wild and no public exploit code.

Affected packages and fixed versions:
- litellm (PyPI): affected from 1.65.5; fixed in 1.85.0
- litellm (PyPI): affected from 1.65.5; fixed in 1.85.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-hhww-mrg2-969h/ (Markdown: https://insights.sbomify.com/GHSA-hhww-mrg2-969h/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hhww-mrg2-969h

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hhww-mrg2-969h/
Summaries are generated and may contain mistakes; the official description above is the record.