# BerriAI litellm has SSRF via Unvalidated spec_path URL in MCP OpenAPI Spec Loader

Advisory record · `GHSA-c693-x898-5g4h`

- **Identifiers:** `GHSA-c693-x898-5g4h` · `CVE-2026-12798` · `PYSEC-2026-4069`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 21 Jun 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Jun 2026, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `litellm` (PyPI): affected `<=1.82.2`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The litellm package, versions up to and including 1.82.2, is vulnerable to server-side request forgery in its MCP OpenAPI spec loader, where the spec_path argument is not validated. A remote attacker can exploit this to make the server send requests to destinations of their choosing, and a public exploit is available. The source gives few details on required privileges. No fix is listed, so restrict untrusted input reaching the spec_path argument until one is released.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0040, the 34th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c693-x898-5g4h)

## Sources

- [GitHub Advisory Database: GHSA-c693-x898-5g4h](https://github.com/advisories/GHSA-c693-x898-5g4h)
- [OSV: GHSA-c693-x898-5g4h](https://osv.dev/vulnerability/GHSA-c693-x898-5g4h)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-12798>
- <https://gist.github.com/YLChen-007/c1104c529975699ba347feedfbe02c5a>
- <https://github.com/BerriAI/litellm>
- <https://vuldb.com/cve/CVE-2026-12798>
- <https://vuldb.com/submit/811290>
- <https://vuldb.com/vuln/372560>
- <https://vuldb.com/vuln/372560/cti>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c693-x898-5g4h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c693-x898-5g4h/>. Everything for agents: <https://agentprime.io/llms.txt>.