# CVE-2026-93088: CVE-2026-93088

> Unauthenticated attackers can execute arbitrary code via unsafe pickle deserialization in the SGLang multimodal generation runtime.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-xv76-mrpv-26pg

## What is CVE-2026-93088?

CVE-2026-93088 is a critical unsafe deserialization vulnerability in SGLang, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLang's multimodal generation runtime is vulnerable to unauthenticated arbitrary code execution because the disaggregated-diffusion orchestrator's DiffusionServer binds an unauthenticated ZeroMQ ROUTER socket to a network interface and passes the final frame of received multipart messages directly to pickle.loads() before any validation occurs.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-93088?


## How do I fix CVE-2026-93088?

Apply the vendor's patch.

## Is CVE-2026-93088 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93088 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93088 and fix it if it is affected.

What it is: CVE-2026-93088 is a critical unsafe deserialization vulnerability in SGLang, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93088 exists.

Affected product: SGLang. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93088/ (Markdown: https://insights.sbomify.com/CVE-2026-93088/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93088
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93088
- OSV: https://osv.dev/vulnerability/CVE-2026-93088

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93088/
Summaries are generated and may contain mistakes; the official description above is the record.