CVE-2026-70620

MediumCVSS 6.8

Published: 04/08/2026(UTC)Updated: 05/08/2026(UTC)Translated: 05/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.26%

18th percentile - higher than 18% of all known CVEs

Summary

The SSRF vulnerability in Odysseus before commit 87babb5 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 to partially read responses from cloud instance metadata services, internal APIs, and other hosts reachable from the server.

Risk Assessment

The risk includes unauthorized access to internal network resources, including cloud metadata and internal APIs, which may lead to sensitive data leakage or privilege escalation in the environment.

Recommendation

It is recommended to immediately update Odysseus to a version containing commit 87babb5 or later and restrict admin privileges to a minimum. Additionally, implement URL validation in the embedding endpoint configuration, blocking private and link-local addresses.

Other vulnerabilities in Odysseus

CVE-2026-70619High
Odysseus before commit bf325f6 contains a missing authorization vulnerability that allows authenticated non-admin users to manage server-wide embedding backend configuration. Attackers can overwrite the configuration, leading to data exfiltration to an attacker-controlled destination or denial of service.

Original NVD description (English source)

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.