# CVE-2026-12798: BerriAI litellm MCP OpenAPI Spec Loader openapi_to_mcp_generator.py load_openapi_spec_async server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the MCP OpenAPI Spec Loader to access internal resources.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-c693-x898-5g4h, MINI-9vr8-mrwg-j4jv, MINI-g9h5-v85r-86q7, MINI-hqc2-fxh8-4pmv, MINI-r7pg-vgvm-7c2w, PYSEC-2026-4069

## What is CVE-2026-12798?

CVE-2026-12798 is a medium-severity server-side request forgery vulnerability in BerriAI litellm, published on 21 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in BerriAI litellm up to 1.82.2. Affected by this vulnerability is the function load_openapi_spec_async of the file litellm/proxy/_experimental/mcp_server/openapi_to_mcp_generator.py of the component MCP OpenAPI Spec Loader. This manipulation of the argument spec_path causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-12798?

3 open source packages ship an affected version, including litellm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `litellm` | PyPI | All versions to 1.82.2 | None |
| `litellm` | PyPI | All versions to 1.82.2 | None |
| `litellm` | PyPI | All versions to 1.82.2 | None |

Products: Litellm Litellm.

## How do I fix CVE-2026-12798?

Upgrade to a fixed version.

## Is CVE-2026-12798 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12798 exists.

## Other vulnerabilities in BerriAI litellm

- [CVE-2026-42208](https://insights.sbomify.com/CVE-2026-42208/): BerriAI LiteLLM SQL Injection (critical 9.3, exploited in the wild)
- [CVE-2026-59822](https://insights.sbomify.com/CVE-2026-59822/): BerriAI LiteLLM Improper Authentication (high 8.8, exploited in the wild)
- [CVE-2026-42271](https://insights.sbomify.com/CVE-2026-42271/): BerriAI LiteLLM Command Injection (high 8.7, exploited in the wild)
- [CVE-2024-5751](https://insights.sbomify.com/CVE-2024-5751/): Remote Code Execution in BerriAI/litellm (critical 9.8)
- [CVE-2024-2952](https://insights.sbomify.com/CVE-2024-2952/): Server-Side Template Injection in BerriAI/litellm (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12798 and fix it if it is affected.

What it is: CVE-2026-12798 is a medium-severity server-side request forgery vulnerability in BerriAI litellm, published on 21 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12798 exists.

Affected packages and fixed versions:
- litellm (PyPI): affected all versions up to 1.82.2; no fix listed
- litellm (PyPI): affected all versions up to 1.82.2; no fix listed
- litellm (PyPI): affected all versions up to 1.82.2; no fix listed

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/CVE-2026-12798/ (Markdown: https://insights.sbomify.com/CVE-2026-12798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12798
- OSV: https://osv.dev/vulnerability/CVE-2026-12798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12798/
Summaries are generated and may contain mistakes; the official description above is the record.