CVE-2026-26220 ModelTC CVE debrief

Who should care

Organizations using LightLLM version 1.1.0 and prior should be aware of this critical vulnerability and take immediate action to mitigate the risk. The vulnerability allows unauthenticated remote code execution in PD disaggregation mode, which can have a significant impact on the security of the system.

Technical summary

The vulnerability in LightLLM version 1.1.0 and prior is caused by the PD master node exposing WebSocket endpoints that receive binary frames and pass the data directly to pickle.loads() without authentication or validation. This allows a remote attacker to send a crafted payload and achieve arbitrary code execution. The vulnerability affects LightLLM version 1.1.0 and prior, and organizations using these versions should take immediate action to mitigate the risk. The vulnerability has a significant impact on the security of the system, and defenders should verify the affected scope and severity with the vendor. Limited details are available about the vulnerability, and evidence is limited. Defenders should focus on verifying affected product deployments and implementing compensating controls.

Defensive priority

High

Recommended defensive actions

• Immediately upgrade to a patched version of LightLLM
• Disable PD disaggregation mode if not required
• Implement authentication and validation for WebSocket endpoints
• Monitor for suspicious activity and implement compensating controls
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-02-17T03:16:01.893Z and has not been modified since then. The NVD entry is currently Deferred. There are limited details available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability is caused by the PD master node exposing WebSocket endpoints that receive binary frames and pass the data directly to pickle.loads() without authentication or validation.

Official resources