CVE-2026-7302: SGLang's multimodal generation runtime has an unauthenticated path traversal vulnerability
SGLang's multimodal generation runtime joins the client-supplied upload filename into its upload path without cleaning it. An unauthenticated request to /v1/images/edits or /v1/videos with ../ in the filename writes a file anywhere the server process can write. SGLang 0.5.5 through 0.5.12 is affected and no patch exists.
Published May 18, 2026 · Updated May 29, 2026 · Analysis Oct 27, 2026
What an attacker can do
The helper _save_upload_to_path in the runtime's utils.py (around lines 125-130), called from image_api.py (lines 212-214), builds the destination from the multipart filename. It does not strip directory components or check that the result stays under the uploads directory. A filename with ../ sequences therefore escapes it.
The attacker needs only HTTP access to the API. No login is required. The write is limited by the permissions of the SGLang process, and the attacker controls both the path and the content. That can overwrite configuration or code that the process owns, or drop files such as shell startup scripts, cron entries or Python modules that run later. The researchers' article calls the set of three issues remote code execution but types this CVE as an arbitrary file write, and does not show the step from write to execution. Whether you get code execution depends on what the process can write on your host.
The CVSS 3.1 vector shows high integrity and availability impact, with no confidentiality impact. The multimodal runtime must be enabled.
Who is affected
SGLang 0.5.5 through 0.5.12 with the multimodal generation runtime enabled and its HTTP API (/v1/images/edits, /v1/videos) reachable. Check the version:
pip show sglangThen check how the server is launched and which interface and port the HTTP API listens on.
sglang
- Ecosystem
- PyPI
- Affected
- >= 0.5.5, <= 0.5.12
- Fixed in
- No patched version yet
- Check
pip show sglang
How to fix it
No official patch exists. The packages data lists no patched version, and the researchers report none is available. Their only mitigation is not to expose SGLang's service interfaces to untrusted networks.
Put the API behind an authenticating reverse proxy or a private network, and run the server as an unprivileged user with a read-only file system apart from the upload and output directories. Track the SGLang releases for a fix beyond 0.5.12.
How to tell if you were hit
Search web and proxy logs for multipart uploads to /v1/images/edits or /v1/videos whose filename contains ../ or encoded forms such as %2e%2e. On the host, look for recently modified files outside the uploads directory, especially in the SGLang install directory, home directory, cron locations and shell profiles. Compare file hashes of the SGLang code against a clean install.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
SGLang's multimodal generation runtime is vulnerable to an unauthenticated path traversal vulnerability, allowing an attacker to write arbitrary files anywhere the server process has write access, by including ../ sequences in the upload filename when sent to specific endpoints.
Questions
- Which endpoints are affected by CVE-2026-7302?
The multimodal runtime's /v1/images/edits and /v1/videos endpoints, where the upload filename reaches _save_upload_to_path without sanitization.
- Does this give code execution?
The CVE is an arbitrary file write. The researchers do not explain how it becomes code execution. It can, if the process can overwrite files that are later run, but that depends on your setup.
- Is there a fixed SGLang release?
No. 0.5.12 is the last version listed as vulnerable and no patched release is reported.
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 entriesCVE-2026-10775
SGLang is Vulnerable to DoS via the data_hash Function
low3.6No fixJun 4, 2026CVE-2026-10300
SGLang: Reachable Assertion via lora_path in LoRAManager enables remote Denial of Dervice
low3.7No fixJun 2, 2026CVE-2026-7301
SGLanG: Multimodal scheduler deserializes untrusted pickle data on 0.0.0.0 ROUTER socket
critical9.8No fixMay 18, 2026CVE-2026-7304
SGLang: Unauthenticated RCE via --enable-custom-logit-processor
critical9.8No fixMay 18, 2026CVE-2026-7669
SGLang has an Improper Input Validation/Injection Issue
medium5.6No fixMay 3, 2026CVE-2026-3059
SGLang's multimodal generation module is vulnerable to unauthenticated remote code execution through the ZMQ broker
critical9.8Mar 12, 2026
