# CVE-2026-70620: Odysseus SSRF via Embedding Endpoint Configuration

> Admins can exploit SSRF in Odysseus to access internal network resources and cloud metadata via unvalidated embedding endpoint URLs.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-pp2c-7vpq-xf5f

## What is CVE-2026-70620?

CVE-2026-70620 is a medium-severity server-side request forgery vulnerability in odysseus-dev odysseus, published on 4 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Odysseus before commit 87babb5 contains a server-side request forgery vulnerability that allows admin-privileged attackers to direct the server to probe internal network resources by supplying arbitrary URLs to the embedding endpoint configuration without scheme, host, IP range, or DNS rebind validation. Attackers can submit loopback addresses, RFC 1918 ranges, or link-local addresses through the embedding endpoint API to partially read responses from cloud instance metadata services, internal APIs, and other hosts reachable from the server.

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

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


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

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

## Is CVE-2026-70620 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70620 is a medium-severity server-side request forgery vulnerability in odysseus-dev odysseus, published on 4 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70620 exists.

Affected product: odysseus-dev odysseus. 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-70620/ (Markdown: https://insights.sbomify.com/CVE-2026-70620/index.md)
```

## Sources

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

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