CVE-2026-76850

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-20. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

LMDeploy deserializes disaggregated-serving peer messages with pickle. The handle_zmq_recv coroutine in lmdeploy/pytorch/disagg/conn/engine_conn.py reads peer-to-peer cache-free requests with recv_pyobj(), which deserializes the received bytes with pickle.loads(), and the isinstance check against DistServeCacheFreeRequest runs only after deserialization has already completed. The peer that supplies those bytes is caller-controlled: p2p_connect passes remote_engine_endpoint_info.zmq_address from the request body to connect() on the ZMQ PULL socket, and the POST /distserve/p2p_initialize and /distserve/p2p_connect endpoints in lmdeploy/serve/openai/api_server.py apply no authentication unless the server is started with api_keys, which defaults to None. A remote attacker can direct an engine to pull from a ZMQ endpoint under their control and execute arbitrary code in the engine process. Deployments that do not enable disaggregated serving are not affected, because the receive loop is only started once the migration backend accepts the connection.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
61%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 21, 2026

Advisory Details (7)

Auto-updated Sep 18, 2026
Patch available. Sources: github_release, github_commit.
generic

LMDeploy Remote Code Execution via Unsafe Pickle Deserialization in the Disaggregated Serving Peer Connector | Advisories | VulnCheck

https://www.vulncheck.com/advisories/lmdeploy-remote-code-execution-via-unsafe-pickle-deserialization-in-the-disaggregated-serving-peer-connector
generic

GitHub - InternLM/lmdeploy: LMDeploy is a toolkit for compressing, deploying, and serving LLMs. · GitHub

https://github.com/InternLM/lmdeploy
github_release Patch Available

v0.16.0

Patch available: InternLM/lmdeploy v0.16.0

https://github.com/InternLM/lmdeploy/releases/tag/v0.16.0
generic

lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.py at v0.15.0 · InternLM/lmdeploy · GitHub

https://github.com/InternLM/lmdeploy/blob/v0.15.0/lmdeploy/pytorch/disagg/conn/engine_conn.py#L61
generic

lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.py at v0.15.0 · InternLM/lmdeploy · GitHub

https://github.com/InternLM/lmdeploy/blob/v0.15.0/lmdeploy/pytorch/disagg/conn/engine_conn.py#L79
github_commit

commit f05b4ad8bf2e (InternLM/lmdeploy)

Fix landed in InternLM/lmdeploy commit f05b4ad8bf2e — awaiting tagged release

https://github.com/InternLM/lmdeploy/commit/f05b4ad8bf2e2d84101a1d63b3c44fadd99223b2
generic

[Bug] Unauthenticated pickle deserialization via ZMQ in disaggregated serving → RCE · Issue #4804 · InternLM/lmdeploy · GitHub

https://github.com/InternLM/lmdeploy/issues/4804

Vendor Advisories for CVE-2026-76850(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 50× in last 7d / 213× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 239 total refreshes for this CVE.

  1. 2026-09-21 08:11 UTCGHSA enrichment
  2. 2026-09-21 03:52 UTCGHSA enrichment
  3. 2026-09-20 23:34 UTCEG score recompute
  4. 2026-09-20 23:34 UTCGHSA enrichment
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-20 18:52 UTCGHSA enrichment
  7. 2026-09-20 14:34 UTCGHSA enrichment
  8. 2026-09-20 10:06 UTCGHSA enrichment
  9. 2026-09-20 05:43 UTCGHSA enrichment
  10. 2026-09-20 01:25 UTCGHSA enrichment
  11. 2026-09-19 21:06 UTCGHSA enrichment
  12. 2026-09-19 16:35 UTCEG score recompute
  13. 2026-09-19 16:35 UTCGHSA enrichment
  14. 2026-09-19 12:17 UTCGHSA enrichment
  15. 2026-09-19 07:57 UTCGHSA enrichment
  16. 2026-09-19 03:39 UTCEG score recompute
  17. 2026-09-19 03:39 UTCGHSA enrichment
  18. 2026-09-18 23:20 UTCEG score recompute
  19. 2026-09-18 23:20 UTCGHSA enrichment
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 19:02 UTCGHSA enrichment
  22. 2026-09-18 14:43 UTCGHSA enrichment
  23. 2026-09-18 10:23 UTCGHSA enrichment
  24. 2026-09-18 06:05 UTCGHSA enrichment
  25. 2026-09-18 01:45 UTCGHSA enrichment
Show 75 more
  1. 2026-09-17 21:26 UTCEG score recompute
  2. 2026-09-17 21:26 UTCGHSA enrichment
  3. 2026-09-17 13:18 UTCGHSA enrichment
  4. 2026-09-17 08:59 UTCGHSA enrichment
  5. 2026-09-17 04:41 UTCGHSA enrichment
  6. 2026-09-17 00:22 UTCGHSA enrichment
  7. 2026-09-16 20:04 UTCGHSA enrichment
  8. 2026-09-16 14:43 UTCEG score recompute
  9. 2026-09-16 14:43 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 10:24 UTCGHSA enrichment
  12. 2026-09-16 06:05 UTCEG score recompute
  13. 2026-09-16 06:05 UTCGHSA enrichment
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-16 01:46 UTCGHSA enrichment
  16. 2026-09-15 21:27 UTCGHSA enrichment
  17. 2026-09-15 17:08 UTCGHSA enrichment
  18. 2026-09-15 12:48 UTCGHSA enrichment
  19. 2026-09-15 08:29 UTCGHSA enrichment
  20. 2026-09-15 04:10 UTCEG score recompute
  21. 2026-09-15 04:10 UTCGHSA enrichment
  22. 2026-09-15 03:12 UTCEPSS rescore
  23. 2026-09-14 23:51 UTCGHSA enrichment
  24. 2026-09-14 19:11 UTCGHSA enrichment
  25. 2026-09-14 13:45 UTCGHSA enrichment
  26. 2026-09-14 09:17 UTCGHSA enrichment
  27. 2026-09-14 04:59 UTCGHSA enrichment
  28. 2026-09-14 00:40 UTCGHSA enrichment
  29. 2026-09-13 20:22 UTCEG score recompute
  30. 2026-09-13 20:22 UTCGHSA enrichment
  31. 2026-09-13 16:03 UTCGHSA enrichment
  32. 2026-09-13 11:44 UTCGHSA enrichment
  33. 2026-09-13 07:25 UTCGHSA enrichment
  34. 2026-09-13 03:07 UTCGHSA enrichment
  35. 2026-09-12 22:48 UTCGHSA enrichment
  36. 2026-09-12 18:27 UTCEG score recompute
  37. 2026-09-12 18:27 UTCGHSA enrichment
  38. 2026-09-12 15:02 UTCEPSS rescore
  39. 2026-09-12 14:08 UTCGHSA enrichment
  40. 2026-09-12 09:49 UTCGHSA enrichment
  41. 2026-09-12 05:30 UTCGHSA enrichment
  42. 2026-09-12 01:11 UTCGHSA enrichment
  43. 2026-09-11 20:52 UTCGHSA enrichment
  44. 2026-09-11 16:33 UTCEG score recompute
  45. 2026-09-11 16:33 UTCGHSA enrichment
  46. 2026-09-11 14:53 UTCEPSS rescore
  47. 2026-09-11 12:15 UTCEG score recompute
  48. 2026-09-11 12:14 UTCGHSA enrichment
  49. 2026-09-11 07:13 UTCGHSA enrichment
  50. 2026-09-11 02:54 UTCGHSA enrichment
  51. 2026-09-10 22:35 UTCGHSA enrichment
  52. 2026-09-10 18:16 UTCGHSA enrichment
  53. 2026-09-10 13:56 UTCGHSA enrichment
  54. 2026-09-10 09:37 UTCEG score recompute
  55. 2026-09-10 09:37 UTCGHSA enrichment
  56. 2026-09-10 09:35 UTCEPSS rescore
  57. 2026-09-10 05:10 UTCGHSA enrichment
  58. 2026-09-10 00:52 UTCGHSA enrichment
  59. 2026-09-09 19:24 UTCGHSA enrichment
  60. 2026-09-09 15:05 UTCGHSA enrichment
  61. 2026-09-09 10:46 UTCGHSA enrichment
  62. 2026-09-09 06:27 UTCGHSA enrichment
  63. 2026-09-09 02:09 UTCEG score recompute
  64. 2026-09-09 02:09 UTCGHSA enrichment
  65. 2026-09-08 22:01 UTCEPSS rescore
  66. 2026-09-08 04:41 UTCGHSA enrichment
  67. 2026-09-08 00:22 UTCGHSA enrichment
  68. 2026-09-07 20:04 UTCEG score recompute
  69. 2026-09-07 20:04 UTCGHSA enrichment
  70. 2026-09-07 15:45 UTCGHSA enrichment
  71. 2026-09-07 11:26 UTCGHSA enrichment
  72. 2026-09-07 07:06 UTCGHSA enrichment
  73. 2026-09-07 02:45 UTCGHSA enrichment
  74. 2026-09-06 21:55 UTCGHSA enrichment
  75. 2026-09-06 17:30 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-76850?
CVE-2026-76850 is a critical vulnerability published on August 19, 2026. LMDeploy deserializes disaggregated-serving peer messages with pickle. The handlezmqrecv coroutine in lmdeploy/pytorch/disagg/conn/engineconn.py reads peer-to-peer cache-free requests with recvpyobj(), which deserializes the received bytes with pickle.loads(), and the isinstance check against…
When was CVE-2026-76850 disclosed?
CVE-2026-76850 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76850 actively exploited?
CVE-2026-76850 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 39.2% of all scored CVEs.
What is the CVSS score of CVE-2026-76850?
CVE-2026-76850 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-76850?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76850, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76850

Explore →

Is Your Infrastructure Affected by CVE-2026-76850?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.