sgl-project SGLang up to 0.5.22 Decode Worker bootstrap_host/bootstrap_port server-side request forgery

Summaryinfo

A vulnerability was found in sgl-project SGLang up to 0.5.22. It has been classified as critical. The impacted element is an unknown function of the component Decode Worker. Performing a manipulation of the argument bootstrap_host/bootstrap_port results in server-side request forgery. This vulnerability is known as CVE-2026-112267. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in sgl-project SGLang up to 0.5.22. It has been classified as critical. This affects an unknown code block of the component Decode Worker. The manipulation of the argument bootstrap_host/bootstrap_port with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

SGLang through 0.5.22 in prefill/decode disaggregation mode contains a server-side request forgery vulnerability that allows unauthenticated attackers to trigger outbound requests via client-supplied bootstrap_host and bootstrap_port fields. Attackers sending crafted requests to the Decode worker's /generate endpoint can probe internal hosts and ports and block the shared scheduler loop, delaying other inference requests.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-112267 since 10/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/19/2026).

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Project Management Software

Vendor

• sgl-project

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

Website

• Product: https://github.com/sgl-project/sglang/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion