VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sglang: vulnerability history, versions and safety

sglang is a package in the PyPI ecosystem. Vulert records 20 vulnerabilities for it across 120 releases, from Sep 2025 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded C5 H1 M2 L2 U10
i
15 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
19 in the last 12 months

Most recent disclosure 19 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sglang vulnerabilities

Vulert verdict on sglang 0.5.22 i

Updated on 23 Oct 2026

Careful: 0.5.22 has 15 known vulnerabilities, and 15 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.5.22 — affected i
  • Vulnerabilities on record 20 over 1 year · 19 in the last year i
  • Latest disclosure 19 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 15 i
  • Depended on by 4 packages i
  • Stars 37,244 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for sglang, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.5.22 16 Oct 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.21 01 Oct 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.20 18 Sep 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.19 04 Sep 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.18 21 Aug 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.17 08 Aug 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.16 25 Jul 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.15.post1 14 Jul 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.15 10 Jul 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.14 26 Jun 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.13.post1 15 Jun 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.13 11 Jun 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.12.post1 23 May 2026 C5 H1 M1 L2 U6 non-standard No Details →
0.5.12 16 May 2026 C3 U3 non-standard No Details →
0.5.11 07 May 2026 C3 L1 U4 non-standard No Details →
0.5.10.post1 08 Apr 2026 C3 L2 U5 non-standard No Details →
0.5.10 05 Apr 2026 C3 L2 U5 non-standard No Details →
0.5.10rc0 27 Mar 2026 C3 L2 U8 non-standard No Details →
0.5.9 23 Feb 2026 C5 H1 M1 L2 U9 non-standard No Details →
0.5.8.post1 05 Feb 2026 C5 H1 M1 L2 U9 non-standard No Details →
0.5.8 23 Jan 2026 C5 H1 M1 L2 U9 non-standard No Details →
0.5.7 01 Jan 2026 C5 H1 M1 L2 U9 non-standard No Details →
0.5.6.post2 11 Dec 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.6.post1 08 Dec 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.6 03 Dec 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.5.post3 17 Nov 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.5.post2 12 Nov 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.5.post1 10 Nov 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.5 06 Nov 2025 C5 H1 M1 L2 U9 non-standard No Details →
0.5.4.post3 05 Nov 2025 C3 H1 M1 L2 U7 non-standard No Details →
0.5.4.post2 01 Nov 2025 C3 H1 M1 L2 U7 non-standard No Details →
0.5.4.post1 27 Oct 2025 C3 H1 M1 L2 U7 non-standard No Details →
0.5.4 24 Oct 2025 C3 H1 M1 L2 U7 non-standard No Details →
0.5.3.post3 16 Oct 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.3.post2 15 Oct 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.3.post1 09 Oct 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.3 06 Oct 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.3rc2 06 Oct 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.3rc0 15 Sep 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.2 11 Sep 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.2rc2 05 Sep 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.2rc1 02 Sep 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.2rc0 01 Sep 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.1.post3 27 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.1.post2 25 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.1.post1 24 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.1 23 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.0rc2 14 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.0rc1 13 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.5.0rc0 08 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.10.post2 03 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.10.post1 01 Aug 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.10 31 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9.post6 29 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9.post5 28 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9.post4 26 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9.post3 22 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9.post2 12 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9.post1 09 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.9 06 Jul 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.8.post1 26 Jun 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.8 24 Jun 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.7.post1 16 Jun 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.7 10 Jun 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.6.post5 24 May 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.6.post4 13 May 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.6.post3 09 May 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.6.post2 01 May 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.6.post1 28 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.6 27 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.5.post3 22 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.5.post2 20 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.5.post1 16 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.5 07 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.4.post4 05 Apr 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.4.post3 29 Mar 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.4.post2 27 Mar 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.4.post1 14 Mar 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.4 13 Mar 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.3.post4 06 Mar 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.3.post3 06 Mar 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.3.post2 17 Feb 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.3.post1 17 Feb 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.3 14 Feb 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.2.post4 10 Feb 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.2.post3 07 Feb 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.2.post2 05 Feb 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.2.post1 31 Jan 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.2 27 Jan 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.1.post7 20 Jan 2025 C3 H1 M2 L2 U8 non-standard No Details →
0.4.1.post6 15 Jan 2025 C2 H1 M2 L2 U7 non-standard No Details →
0.4.1.post5 11 Jan 2025 C2 H1 M2 L2 U7 non-standard No Details →
0.4.1.post4 05 Jan 2025 C2 H1 M2 L2 U7 non-standard No Details →
0.4.1.post3 29 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.4.1.post2 29 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.4.1.post1 27 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.4.1 25 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.4.0.post2 21 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.4.0.post1 06 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.4.0 03 Dec 2024 C2 H1 M2 L2 U7 non-standard No Details →
0.3.6.post3 29 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.6.post2 27 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.6.post1 26 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.6 22 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.5.post2 15 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.5.post1 13 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.5 03 Nov 2024 C2 H1 M2 L2 U7 — No Details →
0.3.4.post2 25 Oct 2024 C2 H1 M2 L2 U7 — No Details →
0.3.4.post1 22 Oct 2024 C2 H1 M2 L2 U7 — No Details →
0.3.4 19 Oct 2024 C2 H1 M2 L2 U7 — No Details →
0.3.3.post1 11 Oct 2024 C2 H1 M2 L2 U7 — No Details →
0.3.3 08 Oct 2024 C2 H1 M2 L2 U7 — No Details →
0.3.2 25 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.3.1.post3 21 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.3.1.post2 19 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.3.1.post1 17 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.3.1 15 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.3.0 03 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.2.15 02 Sep 2024 C2 H1 M2 L2 U7 — No Details →
0.2.14.post2 28 Aug 2024 C2 H1 M2 L2 U7 — No Details →

The newest 120 of 159 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 19

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 19 of the 20 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sglang

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-3060: SGLang Package Vulnerability Leading to Unauthenticated Remote Code Execution 9.8 critical 0.5.10 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 Vulnerable to Unauthenticated Remote Code Execution 9.8 critical No fix published 12 Mar 2026
CVE-2026-7301: SGLanG Multimodal Scheduler RCE via Untrusted Pickle Data 9.8 critical No fix published 18 May 2026
CVE-2026-7304: SGLang Unauthenticated Remote Code Execution via Custom Logit Processor 9.8 critical No fix published 18 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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

Is sglang safe to use?

Vulert records 20 vulnerabilities for sglang in PyPI: 5 critical, 1 high, 2 medium and 2 low, plus 10 not yet rated. 15 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is sglang's Vulert package health score?

Vulert scores sglang 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of sglang affected?

Yes. 0.5.22, the version you would install today, has 15 known vulnerabilities, and 15 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of sglang should I use?

0.5.22 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does sglang have?

20 vulnerabilities are recorded for sglang in the PyPI ecosystem: 5 critical, 1 high, 2 medium and 2 low, plus 10 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sglang vulnerabilities disclosed?

19 vulnerabilities were recorded for sglang in the last 12 months, and the oldest entry in this database dates to 09 Sep 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sglang are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.