# CVE-2026-85666: ogx 1.3.1 Server-Side Request Forgery via MCP tool server_url

> Unauthenticated attackers can exploit SSRF in OGX to access internal resources and cloud metadata via MCP tool definitions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-9mg6-c5wp-2g44

## What is CVE-2026-85666?

CVE-2026-85666 is a high-severity server-side request forgery vulnerability in ogx-ai ogx, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OGX (formerly Llama Stack, affected at commit fbe8e0f) contains an unauthenticated server-side request forgery vulnerability in the OpenAI-compatible POST /v1/responses endpoint. MCP tool definitions accept a server_url parameter (along with headers and authorization values) that is fetched server-side without destination validation; the existing validate_url_not_private() guard used for other URL inputs is not applied to server_url. On the default starter configuration, which runs without authentication, a remote unauthenticated attacker can cause the server to open connections to arbitrary internal addresses (including cloud metadata endpoints such as http://169.254.169.254/) and forward attacker-supplied headers and bearer tokens to those destinations.

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

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


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

No fix has been published for CVE-2026-85666 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85666 being exploited?

There is no known exploitation of CVE-2026-85666 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85666 is a high-severity server-side request forgery vulnerability in ogx-ai ogx, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85666 in the wild and no public exploit code.

Affected product: ogx-ai ogx. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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