# CVE-2026-110807: sgl-project SGLang generate Endpoint io_struct.py denial of service

> Remote attackers can cause denial of service in SGLang by manipulating session parameters in the generate endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-9h5h-jqm8-rrcw

## What is CVE-2026-110807?

CVE-2026-110807 is a medium-severity denial of service vulnerability in sgl-project SGLang, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in sgl-project SGLang up to 0.5.19. Affected by this vulnerability is an unknown functionality of the file python/sglang/srt/managers/io_struct.py of the component generate Endpoint. This manipulation of the argument session_params causes denial of service. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-110807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110807 is a medium-severity denial of service vulnerability in sgl-project SGLang, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110807 exists.

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

## Sources

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

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