SGLang 0.5.10.post1 Inference HTTP Endpoint lora_manager.py lora_path assertion

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.4$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in SGLang 0.5.10.post1. The affected element is an unknown function of the file python/sglang/srt/lora/lora_manager.py of the component Inference HTTP Endpoint. Performing a manipulation of the argument lora_path results in assertion. This vulnerability was named CVE-2026-10300. The attack may be initiated remotely. In addition, an exploit is available. The pull request to fix this issue awaits acceptance.

Detailsinfo

A vulnerability was found in SGLang 0.5.10.post1. It has been classified as problematic. This affects some unknown functionality of the file python/sglang/srt/lora/lora_manager.py of the component Inference HTTP Endpoint. The manipulation of the argument lora_path with an unknown input leads to a assertion vulnerability. CWE is classifying the issue as CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. This is going to have an impact on availability.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-10300. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-33833). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.4

VulDB Base Score: 3.7
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Assertion
CWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

05/31/2026 Advisory disclosed
05/31/2026 +0 days VulDB entry created
06/02/2026 +2 days VulDB entry last update

Sourcesinfo

Advisory: 23141
Status: Not defined
Confirmation: 🔒

CVE: CVE-2026-10300 (🔒)
GCVE (CVE): GCVE-0-2026-10300
GCVE (VulDB): GCVE-100-367593
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 05/31/2026 20:16
Updated: 06/02/2026 03:09
Changes: 05/31/2026 20:16 (58), 06/02/2026 03:09 (1)
Complete: 🔍
Submitter: Zyz3366
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #828086: SGLang Project (sgl-project) SGLang 0.5.10.post1 Reachable Assertion (by Zyz3366)

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!