# CVE-2026-92971: InternLM LMDeploy through 0.17.0 Assertion Denial of Service

> Unauthenticated attackers can crash the InternLM LMDeploy inference engine by submitting a migration request with empty block IDs, causing service disruption.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-3j7h-8qqw-4p7v

## What is CVE-2026-92971?

CVE-2026-92971 is a high-severity denial of service vulnerability in InternLM lmdeploy, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

InternLM LMDeploy through 0.17.0 contains a reachable assertion vulnerability in the DistServe decode migration loop that allows unauthenticated attackers to terminate the inference engine. Attackers can submit a migration_request with an empty remote_block_ids list to trigger an AssertionError that crashes the engine loop and causes subsequent inference requests to fail.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-92971 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92971 is a high-severity denial of service vulnerability in InternLM lmdeploy, published on 17 Sep 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-92971 exists.

Affected product: InternLM lmdeploy. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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