← back to feed
CVE-2026-119706

CVE-2026-119706

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

EUVD-2026-114111 ↗

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.
InternLM lmdeploy >= 0.9.0, <= 0.18.0
CWE-502 Deserialization of Untrusted Data
ETK-2026-3090Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.3cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
2h 37msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h01m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

LMDeploy 0.9.0 through 0.18.0 is affected by unsafe deserialization in the weight-update API endpoint. A remote attacker who can reach that unauthenticated endpoint may execute operating-system commands as the API server process.

mitigation

Restrict network access to the weight-update endpoint immediately, or disable it where it is not required. Place the API service behind authentication and trusted-network controls until a fixed LMDeploy release 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.
–
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.
–
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 15:16Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-30 15:16Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-119706

this entry in the feed

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

{
  "etk_id": "ETK-2026-3090",
  "cve_id": "CVE-2026-119706",
  "display_id": "CVE-2026-119706",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-114111",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated unsafe deserialization in LMDeploy",
  "summary": "LMDeploy 0.9.0 through 0.18.0 is affected by unsafe deserialization in the weight-update API endpoint. A remote attacker who can reach that unauthenticated endpoint may execute operating-system commands as the API server process.",
  "mitigation": "Restrict network access to the weight-update endpoint immediately, or disable it where it is not required. Place the API service behind authentication and trusted-network controls until a fixed LMDeploy release is available.",
  "vendor": "InternLM",
  "product": "lmdeploy",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.9.0, <= 0.18.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "lmdeploy",
      "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.12160855,
  "t0_at": "2026-10-30T15:16:07.266000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T15:16:07.266000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T15:16:07.266000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119706"
    }
  }
}

published 2026-10-30 15:50Z
last change 2026-10-30 17:45Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.