CVE-2026-103041

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

GHSA-3cfg-rxhx-vc58 ↗EUVD-2026-89482 ↗

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-34, permanent identifier
3d 15h 43msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+423h32m
0
+2h
+4h
+6h
+8h
+10h

description

LightLLM multimodal deployments through version 1.2.0 may expose an RPyC cache service that performs unsafe object deserialization. A remote attacker can run code with the service's privileges if they can reach the unauthenticated cache endpoint.

mitigation

Remove public access to the RPyC cache service and restrict it to trusted hosts or networks; disable it where it is not required. Apply a vendor-provided updated release when one is available, as no fixed version is recorded.

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
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-29 22:51Z
Δ 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-29 22:51Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-34",
  "cve_id": "CVE-2026-103041",
  "display_id": "CVE-2026-103041",
  "ghsa_id": "GHSA-3cfg-rxhx-vc58",
  "euvd_id": "EUVD-2026-89482",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unsafe deserialization in LightLLM RPyC cache service",
  "summary": "LightLLM multimodal deployments through version 1.2.0 may expose an RPyC cache service that performs unsafe object deserialization. A remote attacker can run code with the service's privileges if they can reach the unauthenticated cache endpoint.",
  "mitigation": "Remove public access to the RPyC cache service and restrict it to trusted hosts or networks; disable it where it is not required. Apply a vendor-provided updated release when one is available, as no fixed version is recorded.",
  "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.4889,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.15193005,
  "t0_at": "2026-09-29T22:51:00.960000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-29T22:51:00.960000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T22:51:00.960000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103041"
    }
  }
}

published 2026-09-29 23:11Z
last change 2026-10-21 05:31Z

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.