Is CVE-2026-10300 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10300 being exploited in the wild.

How severe is CVE-2026-10300?

Low severity, with a CVSS score of 3.7, published 1 June 2026.

Which products and versions are affected?

sglang (PyPI) ECOSYSTEM:introduced=0,last_affected=0.5.10.post1; SGLang Project SGLang <= 0.5.10.post1, 0.5.10.post1.

Is there a fix for CVE-2026-10300?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-10300 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-10300?

Check whether you run sglang (PyPI) or SGLang Project SGLang at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10300: SGLang reachable assertion in LoRA manager scheduler admission

Q: Is there a fix for CVE-2026-10300?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-10300 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-10300?

Check whether you run sglang (PyPI) or SGLang Project SGLang at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10300 · Severity: low · CVSS 3.7 · Published 2026-06-01

SGLang is an open-source framework used for serving large language models (LLMs). A vulnerability in its LoRA (Low-Rank Adaptation) management component allows a remote attacker to crash the inference server by sending specific concurrent requests. This results in a denial of service, making the AI model unavailable to users and requiring a manual restart of the service.

Technologies: sglang (PyPI), SGLang Project SGLang. Vendors: PyPI, SGLang Project.

Quick answers

Is CVE-2026-10300 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10300 being exploited in the wild.
How severe is CVE-2026-10300?: Low severity, with a CVSS score of 3.7, published 1 June 2026.
Which products and versions are affected?: sglang (PyPI) ECOSYSTEM:introduced=0,last_affected=0.5.10.post1; SGLang Project SGLang <= 0.5.10.post1, 0.5.10.post1.
Is there a fix for CVE-2026-10300?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-10300 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-10300?: Check whether you run sglang (PyPI) or SGLang Project SGLang at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Reachable Assertion (CWE-617) exists in SGLang versions up to 0.5.10.post1 within the `python/sglang/srt/lora/lora_manager.py` file. The vulnerability is triggered when the scheduler constructs a batch containing more LoRA adapters than the limit defined by `--max-loras-per-batch`. Specifically, if concurrent requests arrive for N adapters plus a base-model request, the scheduler fails to enforce the cap, leading to a hard assertion failure in `lora_manager.fetch_new_loras()`. This unhandled exception propagates, causing the scheduler process to terminate and the HTTP inference endpoint to become unresponsive. While the attack can be launched remotely, it is classified as high complexity because it requires precise timing of concurrent requests to specific adapter configurations. A fix has been proposed in the project's repository.

Affected products

sgl-project SGLang <= 0.5.10.post1

Identifiers

CVE-2026-10300
GHSA-m2jr-x4gq-5rmj
PYSEC-2026-3064

Timeline

2026-06-01: disclosed: NVD publication date
2026-06-02: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.