cve.bz

CVE-2026-112082 sgl-project sglang: Improper Resource Shutdown or Release

7.7 highEPSS 0.6%

High (7.7) in sgl-project sglang. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability was identified in sgl-project SGLang up to 0.5.19. This impacts the function Scheduler.expert_distribution_handle of the file python/sglang/srt/eplb/expert_distribution.py of the component Expert-Distribution Recording Endpoint. Such manipulation leads to denial of service. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.

Severity

CVSS 4.0

7.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-112082 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112082?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112082?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112082 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
sgl-project SGLang0.5.0
sgl-project SGLang0.5.1
sgl-project SGLang0.5.2
sgl-project SGLang0.5.3
sgl-project SGLang0.5.4
sgl-project SGLang0.5.5
sgl-project SGLang0.5.6
sgl-project SGLang0.5.7
sgl-project SGLang0.5.8
sgl-project SGLang0.5.9
sgl-project SGLang0.5.10
sgl-project SGLang0.5.11
sgl-project SGLang0.5.12
sgl-project SGLang0.5.13
sgl-project SGLang0.5.14
sgl-project SGLang0.5.15
sgl-project SGLang0.5.16
sgl-project SGLang0.5.17
sgl-project SGLang0.5.18
sgl-project SGLang0.5.19

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON