sgl-project SGLang up to 0.5.19 Expert-Distribution Recording Endpoint expert_distribution.py Scheduler.expert_distribution_handle denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 2.02+ |
Summary
A vulnerability marked as critical has been reported in sgl-project SGLang up to 0.5.19. Affected is the function Scheduler.expert_distribution_handle of the file python/sglang/srt/eplb/expert_distribution.py of the component Expert-Distribution Recording Endpoint. Performing a manipulation results in denial of service.
This vulnerability is identified as CVE-2026-112082. The attack can be initiated remotely. Additionally, an exploit exists.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability, which was classified as critical, was found in sgl-project SGLang up to 0.5.19. This affects the function Scheduler.expert_distribution_handle of the file python/sglang/srt/eplb/expert_distribution.py of the component Expert-Distribution Recording Endpoint. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-112082. 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 and a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The pull request to fix this issue awaits acceptance.
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.
Product
Type
Vendor
Name
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
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.5
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/18/2026 Advisory disclosed10/18/2026 VulDB entry created
10/18/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 42071
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-112082 (🔒)
GCVE (CVE): GCVE-0-2026-112082
GCVE (VulDB): GCVE-100-421761
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/18/2026 16:29Changes: 10/18/2026 16:29 (60)
Complete: 🔍
Submitter: Zyz3366
Cache ID: 216::103
Submit
Accepted
- Submit #1009918: SGLang Project (sgl-project) SGLang 0.5.19 Denial of Service (by Zyz3366)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.