# CVE-2026-33626: LMDeploy Vulnerable to Server-Side Request Forgery (SSRF) via Vision-Language Image Loading

> Attackers can exploit SSRF in LMDeploy's vision module to access internal networks and cloud metadata by providing malicious URLs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** CVE-2025-62167, GHSA-6w67-hwm5-92mq, PYSEC-2026-2607

## What is CVE-2026-33626?

CVE-2026-33626 is a high-severity server-side request forgery vulnerability in InternLM lmdeploy, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LMDeploy is a toolkit for compressing, deploying, and serving large language models. Versions prior to 0.12.3 have a Server-Side Request Forgery (SSRF) vulnerability in LMDeploy's vision-language module. The `load_image()` function in `lmdeploy/vl/utils.py` fetches arbitrary URLs without validating internal/private IP addresses, allowing attackers to access cloud metadata services, internal networks, and sensitive resources. Version 0.12.3 patches the issue.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-33626?

3 open source packages ship an affected version, including lmdeploy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lmdeploy` | PyPI | All versions to 0.12.2 | None |
| `lmdeploy` | PyPI | All versions to 0.12.2 | None |
| `lmdeploy` | PyPI | All versions to 0.12.2 | None |

Products: Internlm Lmdeploy.

## How do I fix CVE-2026-33626?

No fix has been published for CVE-2026-33626 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33626 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33626 exists.

Public exploit code:

- https://github.com/rootdirective-sec/CVE-2026-33626-Lab (github_poc): https://github.com/rootdirective-sec/CVE-2026-33626-Lab
- LMDeploy - Server-Side Request Forgery (nuclei): http/cves/2026/CVE-2026-33626.yaml

## Other vulnerabilities in InternLM lmdeploy

- [CVE-2025-67729](https://insights.sbomify.com/CVE-2025-67729/): lmdeploy vulnerable to Arbitrary Code Execution via Insecure Deserialization in torch.load() (high 8.8)
- [CVE-2026-63764](https://insights.sbomify.com/CVE-2026-63764/): LMDeploy Server-Side Request Forgery via HTTP Redirect Bypass (high 7.7)
- [CVE-2025-3162](https://insights.sbomify.com/CVE-2025-3162/): InternLM LMDeploy PT File utils.py load_weight_ckpt deserialization (medium 4.8)
- [CVE-2025-3163](https://insights.sbomify.com/CVE-2025-3163/): InternLM LMDeploy conf.py open code injection (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33626 and fix it if it is affected.

What it is: CVE-2026-33626 is a high-severity server-side request forgery vulnerability in InternLM lmdeploy, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33626 exists.

Affected packages and fixed versions:
- lmdeploy (PyPI): affected all versions up to 0.12.2; no fix listed
- lmdeploy (PyPI): affected all versions up to 0.12.2; no fix listed
- lmdeploy (PyPI): affected all versions up to 0.12.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33626/ (Markdown: https://insights.sbomify.com/CVE-2026-33626/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33626
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33626
- OSV: https://osv.dev/vulnerability/CVE-2026-33626

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33626/
Summaries are generated and may contain mistakes; the official description above is the record.