Quick answers
- Is CVE-2026-103395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103395 being exploited in the wild.
- How severe is CVE-2026-103395?
- Critical severity, with a CVSS score of 9.8, published 30 September 2026.
- Which products and versions are affected?
- ModelTC LightLLM through 1.2.0.
- Is there a fix for CVE-2026-103395?
- 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-103395 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-103395?
- Check whether you run ModelTC LightLLM 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 is unsafe deserialization (CWE-502) combined with missing authentication (CWE-306). The visual_only_manager.py starts an RPyC ThreadedServer with allow_pickle enabled, no authentication, and listening on 0.0.0.0. The exposed_remote_infer_images() method calls obtain() on attacker-supplied arguments, which deserializes pickled objects; an attacker sends a pickled object with a __reduce__ gadget to achieve RCE before the method validates input as a list.
Affected products
- ModelTC LightLLM through 1.2.0
Timeline
- 2026-09-30: disclosed