# CVE-2026-7302: CVE-2026-7302

> Unauthenticated attackers can write arbitrary files via path traversal in upload filenames, potentially leading to code execution or data modification.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** No
- **Published:** 18 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-qwrp-wghp-94q2, PYSEC-2026-538

## What is CVE-2026-7302?

CVE-2026-7302 is a critical path traversal vulnerability in SGLang, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLangs 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.

Weakness: CWE-35 (Path Traversal: '.../...//')

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

3 open source packages ship an affected version, including sglang. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sglang` | PyPI | From 0.5.5 to 0.5.12 | None |
| `sglang` | PyPI | From 0.5.5 to 0.5.12 | None |
| `sglang` | PyPI | From 0.5.5 to 0.5.12 | None |

Products: Lmsys Sglang.

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

No fix has been published for CVE-2026-7302 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7302 being exploited?

There is no known exploitation of CVE-2026-7302 in the wild and no public exploit code.

## Other vulnerabilities in SGLang

- [CVE-2026-15969](https://insights.sbomify.com/CVE-2026-15969/): CVE-2026-15969 (critical 9.8)
- [CVE-2026-15971](https://insights.sbomify.com/CVE-2026-15971/): CVE-2026-15971 (critical 9.8)
- [CVE-2026-15976](https://insights.sbomify.com/CVE-2026-15976/): CVE-2026-15976 (critical 9.8)
- [CVE-2026-7301](https://insights.sbomify.com/CVE-2026-7301/): CVE-2026-7301 (critical 9.8)
- [CVE-2026-7304](https://insights.sbomify.com/CVE-2026-7304/): CVE-2026-7304 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7302 is a critical path traversal vulnerability in SGLang, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7302 in the wild and no public exploit code.

Affected packages and fixed versions:
- sglang (PyPI): affected from 0.5.5 up to 0.5.12; no fix listed
- sglang (PyPI): affected from 0.5.5 up to 0.5.12; no fix listed
- sglang (PyPI): affected from 0.5.5 up to 0.5.12; no fix listed

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-7302/ (Markdown: https://insights.sbomify.com/CVE-2026-7302/index.md)
```

## Sources

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

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