CVE-2026-70620: Odysseus SSRF via Embedding Endpoint Configuration
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-08-04).
Weakness: Server-Side Request Forgery (SSRF)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing high privileges and no user interaction. Impact: confidentiality none, integrity none, availability none. 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
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| odysseus-dev odysseus | before 87babb58d578 (git commit) | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- Patch Commit (patch)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-70620 Odysseus Embedding Endpoint SSRF via url Parameter. Add them to your Suricata rule set and reload.
Show the rules
# CVE-2026-70620 - Odysseus SSRF: POST /api/embeddings/endpoint takes a "url" form field
# used for a server-side fetch with no scheme/host/IP/DNS-rebind validation. Flags an
# embedding-endpoint request whose url targets a loopback/RFC1918/link-local/metadata host.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-70620 Odysseus Embedding Endpoint SSRF via url Parameter"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/embeddings/endpoint"; nocase; fast_pattern; http.request_body; content:"url="; nocase; pcre:"/(?:^|&)url=https?(?:%3a|:)(?:%2f%2f|\/\/)(?:127\.|10\.|0\.|169\.254\.|192\.168\.|172\.(?:1[6-9]|2[0-9]|3[01])\.|localhost|%5b?::1|metadata)/i"; classtype:web-application-attack; reference:cve,CVE-2026-70620; reference:url,https://www.exploit.observer/?keyword=CVE-2026-70620&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=odysseus&match=exact; sid:1094605; rev:1;)
CVE-2026-70620.rules on GitHub
References
Vendor advisories and patches
- Patch Commit (patch)
Exploit code
- Researcher Blog (technical-description, exploit)
- Researcher Disclosure (technical-description, exploit)
Technical analysis and advisories
- Pull Request (issue-tracking)
- https://www.vulncheck.com/advisories/odysseus-ssrf-via-embedding-endpoint-configuration (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.