Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-76850: Remote Code Execution in LMDeploy Disaggregated-Serving Peer Connector

Published Aug 19, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS1.3%71st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Internlm
IdentifiersCVE-2026-76850CWE-502 · Deserialization of Untrusted Data

CVE-2026-76850 is a remote code execution vulnerability in InternLM LMDeploy affecting versions 0.9.2 and later before 0.16.0. The flaw is caused by unsafe deserialization of peer-to-peer messages in the disaggregated-serving component. In the vulnerable code path, the handle_zmq_recv coroutine in the disaggregated connection logic reads peer messages using recv_pyobj(), which deserializes attacker-supplied data with Python pickle before any effective type validation occurs. Although the code later checks whether the resulting object is a DistServeCacheFreeRequest instance, that validation happens only after deserialization has already completed. The peer endpoint supplying the serialized data is attacker-controllable because the disaggregated-serving connection workflow accepts a remote ZMQ address from request data and uses it to establish the peer connection. When the relevant API endpoints are exposed without authentication, which occurs by default unless API keys are explicitly configured, a remote attacker can cause the engine to connect to a malicious endpoint and deserialize crafted pickle data, resulting in arbitrary code execution in the engine process. Deployments that do not enable disaggregated serving are not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote code execution in the LMDeploy engine process. An attacker can execute arbitrary Python code with the privileges of the affected service, which can lead to full compromise of the confidentiality, integrity, and availability of data and workloads handled by that process. Depending on deployment architecture, this may also enable model service takeover, tampering with inference operations, access to sensitive application data, and further movement within the hosting environment.

Mitigation

If you can’t patch tonight, do this now.

Disable disaggregated serving where it is not required. Do not expose the affected peer-initialization and peer-connection API endpoints to untrusted networks. Configure API key authentication instead of leaving the server at the default unauthenticated setting. Restrict ZMQ peer connectivity so the engine can communicate only with trusted, preapproved endpoints, using network segmentation, firewall policy, and egress controls to prevent connections to attacker-controlled peers.

Remediation

Patch, then assume compromise.

Upgrade LMDeploy to version 0.16.0 or later, which contains the vendor fix for this issue. If immediate upgrade is not possible, remove or disable the vulnerable disaggregated-serving functionality until a fixed release can be deployed. Review the disaggregated peer connection design to ensure untrusted data is never deserialized with pickle and that peer endpoints cannot be arbitrarily supplied by unauthenticated callers.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
InternlmLmdeployapplication
FAQ

Frequently asked questions

Is CVE-2026-76850 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-76850 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76850?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-76850.
Is there a patch for CVE-2026-76850?
Upgrade LMDeploy to version 0.16.0 or later, which contains the vendor fix for this issue. If immediate upgrade is not possible, remove or disable the vulnerable disaggregated-serving functionality until a fixed release can be deployed.
What products are affected by CVE-2026-76850?
Internlm Lmdeploy.
How severe is CVE-2026-76850?
CVE-2026-76850 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 1.3% (71st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity10Community discussion across Reddit, Mastodon, and other social sources.