CVE-2026-33625

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

LMDeploy is a toolkit for compressing, deploying, and serving large language models. Versions 012.1 through 0.12.2 contain a code injection vulnerability in lmdeploy/pytorch/config.py line 620 that allows an attacker to execute arbitrary Python code by publishing a malicious HuggingFace model with a crafted quantization_config.quant_dtype value. When a user loads the model with lmdeploy, the quant_dtype is passed to eval(f'torch.{quant_dtype}') without any validation. Version 0.12.3 contains a patch.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 18, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_release.
github_release Patch Available

v0.12.3

Patch available: InternLM/lmdeploy v0.12.3

https://github.com/InternLM/lmdeploy/releases/tag/v0.12.3
github Patch Available🟡 PoC Available

Arbitrary code execution via eval() of untrusted quant_dtype in model config loading · Advisory · InternLM/lmdeploy · GitHub

https://github.com/InternLM/lmdeploy/security/advisories/GHSA-3hmm-rh5q-gwwr

Vendor Advisories for CVE-2026-33625(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
lmdeploy0.12.1, 0.12.2
  • 0.12.1 up to 0.12.3: fixed in 0.12.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 01:26 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 16:28 UTCEG score recompute
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-02 18:30 UTCEG score recompute
  6. 2026-10-01 20:32 UTCEG score recompute
  7. 2026-10-01 19:49 UTCEPSS rescore
  8. 2026-09-30 22:25 UTCEG score recompute
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 00:25 UTCEG score recompute
  11. 2026-09-29 00:41 UTCEG score recompute
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 15:44 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 17:40 UTCEG score recompute
  16. 2026-09-26 15:58 UTCEPSS rescore
  17. 2026-09-26 06:36 UTCEG score recompute
  18. 2026-09-26 00:26 UTCEPSS rescore
  19. 2026-09-24 21:38 UTCEG score recompute
  20. 2026-09-24 01:21 UTCEG score recompute
  21. 2026-09-22 16:23 UTCEG score recompute
  22. 2026-09-22 15:20 UTCEG score recompute
  23. 2026-09-21 23:23 UTCEG score recompute
  24. 2026-09-21 01:24 UTCEG score recompute
  25. 2026-09-20 20:15 UTCEPSS rescore
Show 4 more
  1. 2026-09-19 16:25 UTCEG score recompute
  2. 2026-09-18 18:27 UTCEG score recompute
  3. 2026-09-18 17:19 UTCEG score recompute
  4. 2026-09-18 17:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-33625?
CVE-2026-33625 is a high vulnerability published on September 18, 2026. LMDeploy is a toolkit for compressing, deploying, and serving large language models. Versions 012.1 through 0.12.2 contain a code injection vulnerability in lmdeploy/pytorch/config.py line 620 that allows an attacker to execute arbitrary Python code by publishing a malicious HuggingFace model with…
When was CVE-2026-33625 disclosed?
CVE-2026-33625 was first published on September 18, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33625 actively exploited?
CVE-2026-33625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33625?
CVE-2026-33625 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-33625?
A fix for CVE-2026-33625 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33625 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33625

Explore →

Is Your Infrastructure Affected by CVE-2026-33625?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.