# LMDeploy has Server-Side Request Forgery (SSRF) via Vision-Language Image Loading Advisory record · `GHSA-6w67-hwm5-92mq` - **Identifiers:** `GHSA-6w67-hwm5-92mq` · `CVE-2026-33626` · `PYSEC-2026-2607` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** Yes: CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html) - **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md) - **Published:** 21 Apr 2026 - **Updated:** 13 Jul 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 21 Apr 2026, 15:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 7.5 (7.0 or more) and EPSS 0.45 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `lmdeploy` (PyPI): affected `<=0.12.2`; no fixed version yet ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > LMDeploy versions up to and including 0.12.2 are affected by a server-side request forgery in the vision-language image loading code, where URLs are fetched without checking for internal or private addresses. An attacker who can send requests to a deployed server with a vision-language model can make it fetch internal resources, such as cloud metadata services, and so reach data not exposed to the internet. The source lists no fixed version, though it states that versions prior to 0.12.3 are affected. Written 6 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 CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.45, the 98th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:59 UTC: First seen by agentprime - 31 Oct 2026, 14:59 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6w67-hwm5-92mq) ## Sources - [GitHub Advisory Database: GHSA-6w67-hwm5-92mq](https://github.com/advisories/GHSA-6w67-hwm5-92mq) - [OSV: GHSA-6w67-hwm5-92mq](https://osv.dev/vulnerability/GHSA-6w67-hwm5-92mq) - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .