xorbitsai xoscar Insecure Deserialization Flaw (CVE-2026-49950) Rated CVSS 9.3
A newly published critical vulnerability in xorbitsai xoscar carries a CVSS score of 9.3. Here is what is affected and how to respond.
Key points
- CVE-2026-49950 affects xorbitsai xoscar.
- CVSS 9.3 (Critical).
- No exploitation confirmed yet.
A critical insecure deserialization tracked as CVE-2026-49950 has been published in the National Vulnerability Database for xorbitsai xoscar, with a CVSS base score of 9.3.
At a glance
- CVE
- CVE-2026-49950
- Product
- xorbitsai xoscar
- CVSS
- 9.3 Critical
- Weakness
- insecure deserialization
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Xorbits Xoscar through 0.11.2 contains an unauthenticated deserialization vulnerability that allows remote attackers to execute arbitrary code by sending crafted data over the actor-pool TCP channel. Attackers can exploit SocketChannel.recv() passing unvalidated data to cloudpickle.loads(), which triggers pickle __reduce__ gadget execution before message type validation, achieving remote code execution as the server process which commonly runs as root on GPU nodes.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Xorbitsai | xoscar | up to 0.11.2 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
Background: Insecure deserialization
Look for base64-encoded parameters, unexpected object instantiation, or state changes that bypass authentication. Inspect input handling for unvalidated deserialization. Use allowlists for expected data types and verify integrity with digital signatures to prevent arbitrary code execution.
Read the full guide: Warning Signs of Insecure Deserialization in Web Applications
What to do and how to stay safe: CVE-2026-49950
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-49950?
CVE-2026-49950 is a insecure deserialization vulnerability in xorbitsai xoscar.
How severe is CVE-2026-49950?
It has a CVSS score of 9.3 Critical.
Is CVE-2026-49950 being exploited?
There is no public confirmation of exploitation at the time of publication.
