Xorbits Xoscar Critical RCE via Unauthenticated TCP Channel Deserialization in CVE-2026-49950

Xorbits Xoscar versions through 0.11.2 contain a critical unauthenticated deserialization vulnerability. Remote attackers can achieve full remote code execution by sending crafted data over the actor-pool TCP channel.

What happened

The vulnerability, tracked as CVE-2026-49950, is classified as Critical with a CVSS score of 9.3 according to the National Vulnerability Database. The flaw stems from how the software handles incoming data. Specifically, the SocketChannel.recv() function passes unvalidated input directly to cloudpickle.loads(). This processing happens before the system performs message type validation.

As a result, the pickle __reduce__ gadget executes immediately. Attackers can exploit this sequence to run arbitrary code on the target system. The executed code runs with the privileges of the server process. In many deployments, this server process operates as root on GPU nodes. This elevated privilege level amplifies the potential impact of the exploit significantly.

Why it matters

The combination of unauthenticated access and high-privilege execution makes this flaw particularly dangerous. Security teams must recognize that the actor-pool TCP channel is the entry point. Because the deserialization occurs before validation, standard input checks may not stop the attack. The use of cloudpickle.loads() on untrusted data is the core technical failure here.

Organizations using Xorbits Xoscar up to version 0.11.2 are exposed. The vulnerability is associated with CWE-502, which covers dangerous use of deserialization. The source material does not mention a fix or update. Teams relying on this software for distributed computing tasks need to assess their exposure immediately.

What to watch

• Monitor the actor-pool TCP channel for unusual traffic patterns.
• Check for unexpected process spawns or privilege escalation attempts.
• Look for signs of pickle gadget execution in server logs.
• Verify that all Xorbits Xoscar instances are not running vulnerable versions.

Signals worth monitoring

Security operations teams should focus on network and process anomalies associated with deserialization attacks. Look for unexpected outbound connections from GPU nodes or sudden spikes in CPU usage during idle periods. Check application logs for errors related to pickle or cloudpickle processing. Investigate any instance where the server process executes commands outside its normal workflow. Verify that no untrusted data is being accepted on the actor-pool TCP channel without prior validation.

Background: CVSS score

CVSS provides a standardized vector for exploit difficulty and access requirements, not business value. A high score indicates an easy attack path, not necessarily significant damage. You must contextualize the score with your environment’s exposure, asset value, and compensating controls to determine true risk.

Read the full guide: CVSS Scores: Why High Numbers Mislead Your Risk Assessment

What to do and how to stay safe: Xorbits Xoscar

• Isolate affected Xorbits Xoscar instances from untrusted networks immediately.
• Restrict access to the actor-pool TCP channel using firewall rules.
• Monitor server processes for unauthorized code execution or privilege changes.
• Await official guidance from the vendor before applying any unverified changes.

General security guidance from the Firewall Chronicle newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Which versions of Xorbits Xoscar are affected by CVE-2026-49950?

All versions of Xorbits Xoscar through 0.11.2 are affected by this vulnerability.

How severe is the deserialization flaw in Xorbits Xoscar?

The National Vulnerability Database rates the vulnerability as Critical with a CVSS score of 9.3.

Is there a patch available for this remote code execution flaw?

The source material does not state whether a patch or fix is available.