Quick answers
- Is CVE-2026-111391 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111391 being exploited in the wild.
- How severe is CVE-2026-111391?
- High severity, with a CVSS score of 8.1, published 16 October 2026.
- Which products and versions are affected?
- SGLang Project SGLang 0.5.10 through 0.5.22.
- Is there a fix for CVE-2026-111391?
- 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-111391 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111391?
- 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 Python code injection in the _evaluate_filter() function that fails to properly sandbox eval() operations. An attacker can escape the eval() sandbox through re.search __globals__ to access and execute arbitrary Python code. The vulnerable /dumper/configure endpoint is unauthenticated and processes filter expressions on the next forward pass of the scheduler process.
Affected products
- SGLang Project SGLang 0.5.10 through 0.5.22
Timeline
- 2026-10-16: disclosed