NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · SGLang

CVE-2026-3059: SGLang's multimodal generation module is vulnerable to unauthenticated remote code execution through the ZMQ broker

criticalCVSS 3.1 9.8GHSA-rgq9-fqf5-fv58

SGLang's multimodal generation ZMQ broker (`scheduler_client.py`) passes bytes received from the network straight to `pickle.loads()` with no authentication. Anyone who can reach the broker port gets remote code execution on the server. The pip package `sglang` is affected up to 0.5.9 and the advisory lists 0.5.10 as patched.

Published Mar 12, 2026 · Updated Apr 7, 2026 · Analysis Oct 31, 2026

What an attacker can do

The broker binds to all interfaces (tcp://*) on a port that defaults to the HTTP port plus one, so --port 8000 exposes 8001. It reads raw bytes from the socket and deserializes them with pickle.loads(). A crafted pickle can name a callable that runs during deserialization, so code executes before any application check. The except block handles errors only after that.

The attacker needs network access to the broker port. No account and no user interaction. They get code execution as the SGLang process, which typically holds model weights, API keys and GPU access. The vector is network, low complexity, CVSS 9.8, and the weakness is CWE-502.

Only deployments that use multimodal generation run the broker. Orca Security reports default text-only deployments are not affected. It also reports a working proof of concept exists and that weaponizing it takes little effort.

Who is affected

sglang up to and including 0.5.9, with the multimodal generation module in use. Check:

pip show sglang

Then check whether the broker port (HTTP port plus one by default) is listening on a non-loopback interface.

sglang

Ecosystem
PyPI
Affected
<= 0.5.9
Fixed in
0.5.10
Check
pip show sglang

How to fix it

Upgrade to 0.5.10, the patched version in the advisory.

pip install --upgrade sglang==0.5.10

The Orca write-up, which was published before the fix was listed, advises limiting exposure meanwhile: firewall the broker port to localhost or known internal clients, and disable multimodal generation if you do not use it. Never expose the port to untrusted networks.

How to tell if you were hit

Look for unexpected inbound ZMTP connections on the broker port, and for shells or tools such as sh, curl or nc spawned by the SGLang process. Check outbound connections from the inference host that you did not expect.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

SGLang's multimodal generation module is vulnerable to unauthenticated remote code execution through the ZMQ broker, which deserializes untrusted data using pickle.loads() without authentication.

Questions

Is it exploited in the wild?

Orca Security reported no observed exploitation at publication, but a working proof of concept exists. It is not in CISA's KEV catalog.

Are text-only SGLang deployments affected?

Orca reports that default text-only deployments are not affected. The broker belongs to the multimodal generation module.

Which version fixes it?

sglang 0.5.10 per the advisory. Versions up to 0.5.9 are affected.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More SGLang vulnerabilities

All SGLang entries