Skip to main content
VulnerabilityPublished Updated

CVE-2026-103042: ModelTC LightLLM · Unthrottled Resource Allocation

Affects ModelTC LightLLMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ModelTCLightLLMAffected
  • <=1.2.0
Fixed in–
GitHubLightLLMpkg:github/LightLLMOther threatsAffected
  • <=1.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, avoid running LightLLM with the --pd_trans_mode nccl option or restrict access to the exposed_set_value method to trusted users to prevent exploitation.

Description

LightLLM versions up to 1.2.0 have a memory exhaustion vulnerability in the NCCL control channel when started with the --pd_trans_mode nccl option. This flaw allows unauthenticated attackers to invoke the exposed_set_value method to store unlimited key-value pairs without size restrictions, leading to exhaustion of KV-transfer worker memory. The resulting memory exhaustion causes the worker process to crash and triggers node failure.

References

Community reviews

Loading reviews…