# CVE-2026-112267: SGLang through 0.5.22 SSRF via bootstrap_host and bootstrap_port on Decode Worker

> Unauthenticated attackers can trigger SSRF and cause denial of service in SGLang's decode worker when prefill/decode disaggregation mode is enabled.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/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:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-mg89-3m78-qwqg

## What is CVE-2026-112267?

CVE-2026-112267 is a medium-severity server-side request forgery vulnerability in sgl-project sglang, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLang through 0.5.22 in prefill/decode disaggregation mode contains a server-side request forgery vulnerability that allows unauthenticated attackers to trigger outbound requests via client-supplied bootstrap_host and bootstrap_port fields. Attackers sending crafted requests to the Decode worker's /generate endpoint can probe internal hosts and ports and block the shared scheduler loop, delaying other inference requests.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-112267 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112267 is a medium-severity server-side request forgery vulnerability in sgl-project sglang, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112267 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-112267/ (Markdown: https://insights.sbomify.com/CVE-2026-112267/index.md)
```

## Sources

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

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