Quick answers
- Is CVE-2026-15971 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15971 being exploited in the wild.
- How severe is CVE-2026-15971?
- Informational severity, with a CVSS score of 9.8, published 30 July 2026.
- Which products and versions are affected?
- SGLang Project SGLang <= v0.5.15.
- Is there a fix for CVE-2026-15971?
- 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-15971 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15971?
- 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
A remote code execution (RCE) vulnerability exists in SGLang's optional 'dumper' subsystem. The vulnerability is rooted in the use of an unsafe `eval()` call within a debugging component that lacks sufficient sandboxing. When the `DUMPER_SERVER_PORT` environment variable is set, the dumper HTTP control plane becomes active. An attacker can send specially crafted inference requests that trigger the dumper to evaluate malicious Python code, leading to a sandbox escape and execution of arbitrary commands with the privileges of the SGLang process. This is part of a broader architectural issue where administrative and debugging routes may lack enforced authentication if API keys are not explicitly configured.
Affected products
- SGLang Project SGLang <= v0.5.15
Timeline
- 2026-04-22: disclosed: Initial disclosure to maintainers via GitHub Security Advisories.
- 2026-07-30: advisory: Public disclosure and CERT/CC coordination.