Quick answers
- Is CVE-2026-112270 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112270 being exploited in the wild.
- How severe is CVE-2026-112270?
- Medium severity, with a CVSS score of 6.5, published 19 October 2026.
- Which products and versions are affected?
- SGLang Project SGLang through 0.5.22.
- Is there a fix for CVE-2026-112270?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-112270 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112270?
- Check whether you run SGLang Project SGLang at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an uncontrolled memory allocation flaw in the handle_staging_rsp() function within the Mooncake disaggregation backend. Unauthenticated attackers can determine the rank address via the /route endpoint and send STAGING_RSP messages with extremely large chunk_idx values under new room IDs, causing unbounded memory allocation that exhausts Prefill memory and triggers an out-of-memory condition that kills the scheduler process.
Affected products
- SGLang Project SGLang through 0.5.22
Timeline
- 2026-10-19: disclosed