Live › vulnerability › CVE-2026-119706
InternLM LMDeploy versions 0.9.0 through 0.18.0 deserialize pickled data sent to the /update_weights endpoint without validation. A remote attacker can send a crafted pickle and run OS commands as the api_server process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 16:31 UTC. All times on this page are UTC.
Teams running LMDeploy's api_server with the update_weights endpoint reachable from the network are exposed. The sources do not say whether authentication or a non-default setting is needed to reach the endpoint, so treat any reachable instance as exposed. Local-only deployments with no network access to the API can skip it.
No product ranges from the sources yet.
pip show lmdeploy, and look for it in any requirements or lock files./update_weights endpoint on servers running lmdeploy serve api_server.0.9.0 through 0.18.0; the fixed version is unknown from the sources.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
InternLM LMDeploy 0.9.0 through 0.18.0 contains an unauthenticated remote code execution vulnerability that allows remote attackers to run OS commands by sending pickled data to the /update_weights endpoint. Attackers can submit a base64-encoded crafted pickle in serialized_named_tensors, which ForkingPickler.loads deserializes without validation, executing commands as the api_server process.
This page as .md · .json · in your agent: get_signal("CVE-2026-119706")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.