Server-side Request Forgery (SSRF) Affecting lmdeploy package, versions [0.12.3,0.15.0)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-LMDEPLOY-21693757
- published24 Oct 2026
- disclosed18 Sept 2026
- creditUnknown
Introduced: 18 Sep 2026
CVE NOT AVAILABLE CWE-436 (opens in a new tab)How to fix?
Upgrade lmdeploy to version 0.15.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via _is_safe_url in the URL validation logic, where a discrepancy between how urlparse() and the requests library parse backslash-containing URLs allows an attacker to bypass SSRF protections. When a URL of the form http://127.0.0.1:6666\@1.1.1.1 is supplied, urlparse() treats \ as a regular character and @ as the userinfo-host delimiter, extracting 1.1.1.1 as the hostname and passing the safety check, while requests treats \ as a path separator and connects to 127.0.0.1, reaching internal network resources. An attacker can exploit this to make the server issue requests to arbitrary internal addresses.