Remote service crash via LoRA admission miscount
Published Jun 1, 2026 · Updated Jun 1, 2026
Reachable assertion in SGLang 0.5.10.post1 allows remote attackers to crash an inference server through concurrent LoRA requests. The scheduler omits already admitted chunked-request LoRA IDs when enforcing max_loras_per_batch, so fetch_new_loras receives N+1 IDs and asserts. Exploitation requires LoRA serving plus a concurrency and scheduling state that exceeds the configured batch cap; the resulting SIGQUIT leaves the service unresponsive.
Summary
What happened
Reachable assertion in SGLang 0.5.10.post1 allows remote attackers to crash an inference server through concurrent LoRA requests. The scheduler omits already admitted chunked-request LoRA IDs when enforcing max_loras_per_batch, so fetch_new_loras receives N+1 IDs and asserts. Exploitation requires LoRA serving plus a concurrency and scheduling state that exceeds the configured batch cap; the resulting SIGQUIT leaves the service unresponsive.
The record
- CVE
- CVE-2026-10300
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- SGLang
- Product
- SGLang
- Classifications
- CWE-617, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.5.10.post1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- SGLang concurrent LoRA crash reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo