SGLang up to 0.5.22 Filter Evaluation _evaluate_filter code injection

Summaryinfo

A vulnerability was found in SGLang up to 0.5.22. It has been rated as critical. Affected by this vulnerability is the function _evaluate_filter of the component Filter Evaluation. This manipulation causes code injection. This vulnerability is tracked as CVE-2026-111391. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in SGLang up to 0.5.22 and classified as critical. Affected by this vulnerability is the function _evaluate_filter of the component Filter Evaluation. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

SGLang 0.5.10 through 0.5.22 contains a code injection vulnerability in _evaluate_filter() that allows remote attackers to execute Python code by escaping the eval() sandbox through re.search __globals__. Attackers can send a crafted filter expression to the unauthenticated /dumper/configure endpoint when DUMPER_SERVER_PORT is set, running code in the scheduler process on the next forward pass.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-111391 since 10/15/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/16/2026). The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• SGLang

Version

• 0.5.0
• 0.5.1
• 0.5.2
• 0.5.3
• 0.5.4
• 0.5.5
• 0.5.6
• 0.5.7
• 0.5.8
• 0.5.9
• 0.5.10
• 0.5.11
• 0.5.12
• 0.5.13
• 0.5.14
• 0.5.15
• 0.5.16
• 0.5.17
• 0.5.18
• 0.5.19
• 0.5.20
• 0.5.21
• 0.5.22

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion