sglang
10 published advisories; version 0.5.10 or later fixes all but 6 of them.
- Registry
- PyPI
- Advisories
- 10
- Latest fix
- 0.5.10
- Exploited in the wild
- None listed
6 advisories have no fixed release in any version yet. What can be done meanwhile:
General guidance from ShieldPi, not a vendor fix
- Command or code injection. Remove or disable the affected server or tool, or run it in a sandbox with no secrets in its environment.GHSA-36m8-w8qf-g76p
- Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.GHSA-qwrp-wghp-94q2
- Unsafe deserialization. Do not let it load files, models or data from sources you do not trust, and keep its RPC and socket ports reachable only from localhost or hosts you trust.GHSA-36m8-w8qf-g76p · GHSA-gwv6-pq6m-p3rq
- Missing or bypassable authentication. Do not expose it on a network others can reach, and put authentication you control in front of it, such as an authenticating proxy or a VPN. Binding it to localhost is not enough on its own: a web page open in your browser can still reach it, so require a token as well.GHSA-36m8-w8qf-g76p · GHSA-qwrp-wghp-94q2
Check your projects
shieldpi agent-config checks agent and MCP packages from npm and PyPI, not sglang. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.
osv-scanner scan source -r .Or check a lockfile against ShieldMap in your browser.
Source: github.com/sgl-project/sglang, named in the package metadata (not verified)
0 of the last 10 releases of sglang were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 0.5.23
- 0.5.22
- 0.5.21
- 0.5.20
- 0.5.19
- 0.5.18
- 0.5.17
- 0.5.16
- 0.5.15.post1
- 0.5.15
Green: published with provenance. Grey: without.
OpenSSF Scorecard has not scored this repository.
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].