Quick answers
- Is CVE-2026-112267 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112267 being exploited in the wild.
- How severe is CVE-2026-112267?
- 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-112267?
- 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-112267 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112267?
- 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 a server-side request forgery (SSRF) in SGLang's prefill/decode disaggregation mode, where client-supplied bootstrap_host and bootstrap_port parameters in requests to the Decode worker's /generate endpoint are not properly validated before use in outbound connections. An unauthenticated attacker can exploit this to probe internal hosts and ports or block the shared scheduler loop, delaying other inference requests. No authentication is required, and the attack vector is network-based.
Affected products
- SGLang Project SGLang through 0.5.22
Timeline
- 2026-10-19: disclosed