# CVE-2026-123818: LMDeploy URL parser disagreement permits SSRF filter bypass


- **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
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-39wr-7q6h-cf68

## What is CVE-2026-123818?

CVE-2026-123818 is a high-severity vulnerability in InternLM lmdeploy, published on 9 Nov 2026. 

### Official description

LMDeploy is a toolkit for compressing, deploying, and serving large language models. From 0.12.3 until 0.15.0, _is_safe_url validates remote media URLs with urlparse while requests.Session().get interprets backslashes differently when sending the request. An attacker can provide a URL whose validation hostname appears globally routable but whose request destination resolves to an internal host, bypassing non-global address checks. Applications that accept attacker-controlled remote media URLs can therefore be induced to access internal HTTP services and expose data available from those services. This issue is fixed in version 0.15.0.

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

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

1 open source package ship an affected version, including lmdeploy.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lmdeploy` | PyPI | From 0.12.3 | 0.15.0 |

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

Upgrade lmdeploy to 0.15.0 or later.

## Is CVE-2026-123818 being exploited?

There is no known exploitation of CVE-2026-123818 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123818 is a high-severity vulnerability in InternLM lmdeploy, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123818 in the wild and no public exploit code.

Affected packages and fixed versions:
- lmdeploy (PyPI): affected from 0.12.3; fixed in 0.15.0

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-123818/ (Markdown: https://insights.sbomify.com/CVE-2026-123818/index.md)
```

## Sources

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

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