VulertSecurity VulertSecurity

Vulnerability Database · PyPI · sglang · Version

sglang 0.5.7

0.5.7 is affected by 18 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.5.22.

Critical 10 High 2 Medium 2 Low 4 Unrated 0

All sglang versions & vulnerabilities → Source repository Search the database for this package →
Released 01 Jan 2026 Licence non-standard Also known from other sources 18 Newer releases 159 Database updated 23/Oct/2026

Release and licence data published by PyPI. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

sglang 0.5.7 vulnerabilities

18 vulnerabilities cover sglang 0.5.7. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2026-7301: SGLanG Multimodal Scheduler Vulnerability Leading to RCE via Untrusted Pickle Data 9.8 critical No fix published 29 Jun 2026
CVE-2026-7304: sglang Unauthenticated RCE via --enable-custom-logit-processor 9.8 critical No fix published 29 Jun 2026
CVE-2026-3059: SGLang Remote Code Execution Vulnerability via ZMQ Broker 9.8 critical 0.5.10 29 Jun 2026
CVE-2026-3060: SGLang Package Vulnerability Leading to Unauthenticated Remote Code Execution 9.8 critical 0.5.10 29 Jun 2026
CVE-2026-7304: SGLang Unauthenticated Remote Code Execution via Custom Logit Processor 9.8 critical No fix published 18 May 2026
CVE-2026-7301: SGLanG Multimodal Scheduler RCE via Untrusted Pickle Data 9.8 critical No fix published 18 May 2026
CVE-2026-3060: SGLang Package Vulnerable to Unauthenticated Remote Code Execution 9.8 critical No fix published 12 Mar 2026
CVE-2026-3059: SGLang Remote Code Execution Vulnerability via ZMQ Broker 9.8 critical No fix published 12 Mar 2026
CVE-2026-7302: SGLang Path Traversal Vulnerability Allows Arbitrary File Writing 9.1 critical No fix published 29 Jun 2026
CVE-2026-7302: SGLang Path Traversal Vulnerability Allows Arbitrary File Writing 9.1 critical No fix published 18 May 2026
CVE-2026-3989: SGLangs Insecure Pickle Load Vulnerability in replay_request_dump.py 7.8 high 0.5.10 13 Jul 2026
CVE-2026-3989: SGLangs Insecure Pickle Load Vulnerability in replay_request_dump.py 7.8 high No fix published 12 Mar 2026
CVE-2026-7669: SGLang Improper Input Validation Leading to Remote Deserialization Vulnerability 5.6 medium No fix published 13 Jul 2026
CVE-2026-7669: SGLang Improper Input Validation and Injection Vulnerability 5.6 medium No fix published 03 May 2026
CVE-2026-10300: SGLang Remote Denial of Service via lora_path Manipulation 3.7 low No fix published 13 Jul 2026
CVE-2026-10300: SGLang Remote Denial of Service via lora_path Manipulation 3.7 low No fix published 02 Jun 2026
CVE-2026-10775: SGLang Denial of Service Vulnerability in Cache Handler 3.6 low No fix published 19 Aug 2026
CVE-2026-10775: SGLang Denial of Service Vulnerability in Cache Handler 3.6 low No fix published 04 Jun 2026

Looking for another version, or everything Vulert holds for sglang?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sglang 0.5.7

Is sglang 0.5.7 vulnerable?

Yes. 18 vulnerabilities in the Vulert database cover sglang 0.5.7: 10 critical, 2 high, 2 medium and 4 low. The upgrade Vulert recommends is 0.5.22, and each entry above names the fixed version to move to.

Which version of sglang should I use instead of 0.5.7?

0.5.22 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 0.5.7 the latest release of sglang?

No. 0.5.7 was published 01 Jan 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor sglang for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sglang version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.