# CVE-2026-93688: SGLang through 0.5.19 Unbounded Memory Allocation via bootstrap_room

> Unauthenticated attackers can exhaust memory in SGLang's prefill process by submitting arbitrary bootstrap_room values, causing denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-hpqj-j2xw-q3cx

## What is CVE-2026-93688?

CVE-2026-93688 is a high-severity denial of service vulnerability in sgl-project sglang, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLang through 0.5.19 in prefill/decode disaggregation mode with Mooncake KV transfer backend fails to validate bootstrap_room values, allowing unbounded transfer state allocation. Unauthenticated attackers can reach the decode engine's POST /generate endpoint and submit arbitrary bootstrap_room values to exhaust prefill process memory until out-of-memory termination.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

No fix published yet.

## Is CVE-2026-93688 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93688 is a high-severity denial of service vulnerability in sgl-project sglang, published on 18 Sep 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-93688 in the wild and no public exploit code.

Affected product: sgl-project 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-93688/ (Markdown: https://insights.sbomify.com/CVE-2026-93688/index.md)
```

## Sources

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

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