# CVE-2026-112269: SGLang through 0.5.22 Memory Exhaustion via Unauthenticated Mooncake Decode Registrations

> Network-adjacent attackers can exhaust memory and crash the scheduler by sending unauthenticated registration messages to the Mooncake backend.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-9qhw-7fv2-2hgm

## What is CVE-2026-112269?

CVE-2026-112269 is a high-severity denial of service vulnerability in sgl-project sglang, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SGLang through 0.5.22 with the Mooncake disaggregation backend accepts unauthenticated decode registration messages on the Prefill rank ZMQ PULL socket, allowing denial of service. Network-adjacent attackers can send many registrations with unique mooncake_session_id values and large nested-buffer frames to exhaust Prefill memory until the scheduler is OOM-killed.

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

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


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

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

## Is CVE-2026-112269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112269 is a high-severity denial of service vulnerability in sgl-project sglang, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112269 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-112269/ (Markdown: https://insights.sbomify.com/CVE-2026-112269/index.md)
```

## Sources

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

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