Quick answers
- Is CVE-2026-111392 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111392 being exploited in the wild.
- How severe is CVE-2026-111392?
- Medium severity, with a CVSS score of 4.8, published 16 October 2026.
- Which products and versions are affected?
- SGLang Project SGLang through 0.5.21.
- Is there a fix for CVE-2026-111392?
- 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-111392 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111392?
- 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
SGLang through version 0.5.21 uses caller-supplied mm_hashes values as the key for multimodal prefix-cache lookups without validation. An attacker can send a request via the /generate endpoint with a forged mm_hash matching a known or predicted hash from another request, paired with a different image, to corrupt cached KV entries. This is a cache poisoning vulnerability requiring network access but no authentication.
Affected products
- SGLang Project SGLang through 0.5.21
Timeline
- 2026-10-16: disclosed