CVE-2026-103395

waiting for further signalsZero needs more public information before it can validate it.

GHSA-mw2v-h3wh-mp72 ↗EUVD-2026-89990 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ModelTC LightLLM <= 1.2.0
CWE-502 Deserialization of Untrusted Data
ETK-2026-164, permanent identifier
20d 12h 34msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+8h18m
0
+2h
+4h
+6h
+10h
+12h

description

LightLLM visual_only deployments through 1.2.0 expose an unauthenticated RPyC service that performs unsafe deserialization. An attacker able to reach that service may execute code with the privileges of the LightLLM service account.

mitigation

Immediately restrict the visual RPyC service to trusted network clients and disable pickle deserialization if the deployment supports that configuration. No fixed LightLLM version is recorded; keep the service inaccessible to untrusted networks until a vendor update is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.62%48th percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 14:48Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 14:48Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103395

{
  "etk_id": "ETK-2026-164",
  "cve_id": "CVE-2026-103395",
  "display_id": "CVE-2026-103395",
  "ghsa_id": "GHSA-mw2v-h3wh-mp72",
  "euvd_id": "EUVD-2026-89990",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unsafe deserialization in LightLLM visual deployments",
  "summary": "LightLLM visual_only deployments through 1.2.0 expose an unauthenticated RPyC service that performs unsafe deserialization. An attacker able to reach that service may execute code with the privileges of the LightLLM service account.",
  "mitigation": "Immediately restrict the visual RPyC service to trusted network clients and disable pickle deserialization if the deployment supports that configuration. No fixed LightLLM version is recorded; keep the service inaccessible to untrusted networks until a vendor update is available.",
  "vendor": "ModelTC",
  "product": "LightLLM",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "LightLLM",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0062,
  "epss_percentile": 0.4859,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.586766266666666,
  "t0_at": "2026-09-30T14:48:55.734000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T14:48:55.734000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T14:48:55.734000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103395"
    }
  }
}

published 2026-09-30 22:58Z
last change 2026-10-21 09:20Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.