# LMDeploy has an SSRF bypass

Advisory record · `GHSA-39wr-7q6h-cf68`

- **Identifiers:** `GHSA-39wr-7q6h-cf68`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-436](https://cwe.mitre.org/data/definitions/436.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md) · [CWE-436](https://agentprime.io/advisories/tag/cwe-436.md)
- **Published:** 18 Sept 2026
- **Updated:** 18 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Sept 2026, 17:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `lmdeploy` (PyPI): affected `>=0.12.3, <0.15.0`; fixed in `0.15.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> lmdeploy versions 0.12.3 up to 0.15.0 are vulnerable to a server-side request forgery bypass. A crafted URL passes the URL safety check by resolving to a public host, but the request library sends it to an internal address, which lets an attacker reach internal services. Upgrade to lmdeploy 0.15.0.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-39wr-7q6h-cf68)

## Sources

- [GitHub Advisory Database: GHSA-39wr-7q6h-cf68](https://github.com/advisories/GHSA-39wr-7q6h-cf68)
- [OSV: GHSA-39wr-7q6h-cf68](https://osv.dev/vulnerability/GHSA-39wr-7q6h-cf68)
- <https://github.com/InternLM/lmdeploy/security/advisories/GHSA-39wr-7q6h-cf68>
- <https://github.com/InternLM/lmdeploy>
- <https://github.com/InternLM/lmdeploy/releases/tag/v0.15.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-39wr-7q6h-cf68>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-39wr-7q6h-cf68/>. Everything for agents: <https://agentprime.io/llms.txt>.