CVE-2025-10164
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 · uneditedA security flaw has been discovered in lmsys sglang 0.4.6. Affected by this vulnerability is the function main of the file /update_weights_from_tensor. The manipulation of the argument serialized_named_tensors results in deserialization. The attack can be launched remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceA deserialization vulnerability in lmsys sglang 0.4.6 allows remote attackers to execute arbitrary code via the /update_weights_from_tensor endpoint by supplying maliciously crafted serialized tensor data to the serialized_named_tensors argument.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify sglang installation and versionRun 'pip show sglang' or 'pip list | grep sglang' to check if sglang is installed and its version numberAffected if The installed version is exactly 0.4.6 or falls within the 0.4.6 release line (e.g., 0.4.6.x)
-
Locate the update_weights_from_tensor endpointSearch the sglang source code for '/update_weights_from_tensor' or inspect the API routes defined in the server implementationAffected if The endpoint is present in the codebase and registered as an available API route
-
Check if the serialized_named_tensors parameter is handledExamine the handler function for /update_weights_from_tensor to see if it accepts and deserializes the serialized_named_tensors argument without strict validationAffected if The endpoint processes the serialized_named_tensors argument through an unsafe deserialization method (e.g., pickle, torch.load) without sanitization
-
Determine API server network exposureCheck the sglang server startup configuration and running process (e.g., 'ps aux | grep sglang', netstat, or ss) to see if the API listens on 0.0.0.0 or a publicly accessible IP addressAffected if The sglang server is bound to a network interface accessible to untrusted users (e.g., 0.0.0.0 or external IP) and the vulnerable endpoint is enabled
You are affected if sglang version 0.4.6 is installed AND the /update_weights_from_tensor endpoint is exposed to a network where remote attackers can send malicious serialized tensor data.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a patched version of sglang once available. In the interim, restrict network access to the affected endpoint and implement strict input validation on the serialized tensor data before deserialization.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10164 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10164 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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