Quick answers
- Is CVE-2026-119706 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119706 being exploited in the wild.
- How severe is CVE-2026-119706?
- Critical severity, with a CVSS score of 9.8, published 30 October 2026.
- Which products and versions are affected?
- Internlm Lmdeploy 0.9.0 through 0.18.0.
- Is there a fix for CVE-2026-119706?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-119706 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-119706?
- Check whether you run Internlm Lmdeploy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the management.py endpoint handler for /update_weights, which accepts base64-encoded pickle objects in the serialized_named_tensors parameter and deserializes them using ForkingPickler.loads() without validation. An attacker can craft malicious pickle payloads that execute arbitrary code during deserialization. The endpoint requires no authentication and is exposed over the network via the FastAPI server.
Affected products
- InternLM LMDeploy 0.9.0 through 0.18.0
Timeline
- 2026-10-30: disclosed