dbcve.org
SglangApplication · Lmsys

CVE-2026-3060

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to after 0.5.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SGLang' encoder parallel disaggregation system is vulnerable to unauthenticated remote code execution through the disaggregation module, which deserializes untrusted data using pickle.loads() without authentication.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SGLang's encoder parallel disaggregation system contains a critical unauthenticated remote code execution vulnerability. The disaggregation module deserializes untrusted data using Python's pickle.loads() function without any authentication, allowing attackers to execute arbitrary code by sending maliciously crafted pickle payloads.

MitigationReplace pickle.loads() with secure deserialization methods (e.g., JSON, msgpack) and implement proper authentication and input validation on the disaggregation module. If pickle must be used, employ cryptographic signature verification before deserialization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SglangApplication
Affected:>= 0.5.5, <= 0.5.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SGLang installation and version
    Run 'pip show sglang' or 'pip list | grep sglang' to find installed version. Check the 'Version:' field.
    Affected if Version is 0.5.5, 0.5.6, 0.5.7, 0.5.8, or 0.5.9 (any version >= 0.5.5 and <= 0.5.9)
  2. Locate the disaggregation module
    Search for files containing 'disaggregat' in the SGLang installation directory, typically under the sglang python package folder. Look for files handling encoder parallel disaggregation.
    Affected if The disaggregation module exists in the installation and contains pickle.loads() calls
  3. Verify if encoder parallel disaggregation is enabled
    Check running configuration files, environment variables, or startup parameters for SGLang. Look for flags like --enable-disaggregation, --encoder-parallel-disaggregation, or similar disaggregation-related settings.
    Affected if Encoder parallel disaggregation feature is enabled in the running configuration
  4. Inspect the disaggregation module code for insecure deserialization
    Open the disaggregation module source file and search for 'pickle.loads' or 'pickle.load' function calls. Verify if they process incoming data without authentication checks.
    Affected if The code uses pickle.loads() on untrusted input without prior authentication or signature verification

You are affected if SGLang version is between 0.5.5 and 0.5.9 inclusive AND the encoder parallel disaggregation feature is enabled, allowing unauthenticated remote attackers to send malicious pickle payloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.5.9
Vendor patch github.com →
Interim mitigation

Replace pickle.loads() with secure deserialization methods (e.g., JSON, msgpack) and implement proper authentication and input validation on the disaggregation module. If pickle must be used, employ cryptographic signature verification before deserialization.

Recommended fix Moderate confidence

Latest stable Sglang release (version > 0.5.9)

  1. 1. Identify the current Sglang version installed in your environment using `pip show sglang` or `python -c "import sglang; print(sglang.__version__)"`
  2. 2. Review the patch details at the vendor commit https://github.com/sgl-project/sglang/pull/20904 to understand what changes were made to fix the unsafe pickle.loads() deserialization
  3. 3. Upgrade to the latest stable Sglang release (version > 0.5.9) which should include the fix: `pip install --upgrade sglang`
  4. 4. Verify the upgrade was successful by checking the installed version
  5. 5. Test that the disaggregation module functions correctly after the upgrade
Caveat Review release notes for any breaking changes between 0.5.9 and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sglang Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3060 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data