CVE-2025-66448

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. 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, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.11.1, vllm has a critical remote code execution vector in a config class named Nemotron_Nano_VL_Config. When vllm loads a model config that contains an auto_map entry, the config class resolves that mapping with get_class_from_dynamic_module(...) and immediately instantiates the returned class. This fetches and executes Python from the remote repository referenced in the auto_map string. Crucially, this happens even when the caller explicitly sets trust_remote_code=False in vllm.transformers_utils.config.get_config. In practice, an attacker can publish a benign-looking frontend repo whose config.json points via auto_map to a separate malicious backend repo; loading the frontend will silently run the backend’s code on the victim host. This vulnerability is fixed in 0.11.1.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
55(Track)
EG Risk 55/100SSVC: Track

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%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

December 1, 2025

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Patch available. Sources: github_pr, github, github_commit.
github Patch Available

Remote code execution via transformers_utils/get_config · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-8fr4-5q9j-m8gm
github_pr

[Chore] Remove Nemotron-Nano-VL config copy

Fix merged in vllm-project/vllm PR #28126 on 2025-11-05 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/28126
github_commit

commit ffb08379d887 (vllm-project/vllm)

Fix landed in vllm-project/vllm commit ffb08379d887 — awaiting tagged release

https://github.com/vllm-project/vllm/commit/ffb08379d8870a1a81ba82b72797f196838d0c86

Vendor Advisories for CVE-2025-66448(14)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-spyre-rhel9:17823529192026-06-25redhat
redhatrhoai/odh-vllm-cpu-rhel9:17782643632026-05-20redhat
redhatrhoai/odh-vllm-cpu-rhel9:17720934362026-03-04redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17709560342026-03-04redhat
redhatrhaiis/vllm-cuda-rhel9:17721605932026-02-27redhat
redhatrhaiis/vllm-rocm-rhel9:17721606252026-02-27redhat
redhatrhaiis/vllm-rocm-rhel9:3.2.5-17655526032025-12-17redhat
redhatrhaiis/vllm-tpu-rhel9:3.2.5-17655526192025-12-15redhat
redhatrhaiis/vllm-rocm-rhel9:3.2.5-17653611802025-12-15redhat
redhatrhaiis/vllm-cuda-rhel9:3.2.5-17655525802025-12-15redhat
redhatrhaiis/model-opt-cuda-rhel9:3.2.2-17648717962025-12-10redhat
redhatrhaiis/vllm-rocm-rhel9:3.2.2-17653790492025-12-10redhat
redhatrhaiis/vllm-cuda-rhel9:3.2.2-17653790882025-12-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.0.1 ... 0.9.2 (67 versions)0.11.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 27× 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.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:11 UTCEPSS rescore
  5. 2026-09-01 13:53 UTCEPSS rescore
  6. 2026-08-30 19:16 UTCEPSS rescore
  7. 2026-08-30 01:21 UTCEPSS rescore
  8. 2026-08-28 21:40 UTCEPSS rescore
  9. 2026-08-27 14:24 UTCEPSS rescore
  10. 2026-08-26 14:45 UTCEPSS rescore
  11. 2026-08-25 13:48 UTCEPSS rescore
  12. 2026-08-24 14:16 UTCEPSS rescore
  13. 2026-08-24 14:02 UTCOSV refresh
  14. 2026-08-23 00:18 UTCEPSS rescore
  15. 2026-08-21 23:48 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:47 UTCEPSS rescore
  19. 2026-08-17 13:46 UTCEPSS rescore
  20. 2026-08-16 14:55 UTCEPSS rescore
  21. 2026-08-16 02:13 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-15 01:29 UTCEPSS rescore
  24. 2026-08-13 21:59 UTCEPSS rescore
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 75 more
  1. 2026-08-11 13:42 UTCEPSS rescore
  2. 2026-08-10 23:59 UTCEPSS rescore
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-09 13:46 UTCEPSS rescore
  5. 2026-08-08 16:36 UTCEPSS rescore
  6. 2026-08-08 08:59 UTCEG score recompute
  7. 2026-08-08 08:59 UTCVendor advisory
  8. 2026-08-07 16:26 UTCEPSS rescore
  9. 2026-08-06 13:46 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 15:09 UTCEPSS rescore
  13. 2026-08-04 10:37 UTCEPSS rescore
  14. 2026-08-03 10:35 UTCEPSS rescore
  15. 2026-08-02 02:26 UTCEPSS rescore
  16. 2026-08-01 04:15 UTCEPSS rescore
  17. 2026-07-30 16:27 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-28 15:35 UTCEPSS rescore
  20. 2026-07-27 14:12 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-24 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 14:11 UTCOSV refresh
  29. 2026-07-23 03:01 UTCEG score recompute▲ 1.70
  30. 2026-07-22 14:08 UTCEPSS rescore
  31. 2026-07-21 15:24 UTCEPSS rescore
  32. 2026-07-20 17:08 UTCEPSS rescore
  33. 2026-07-19 14:30 UTCEPSS rescore
  34. 2026-07-19 14:30 UTCEPSS rescore
  35. 2026-07-19 02:28 UTCEPSS rescore
  36. 2026-07-18 10:04 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-16 17:02 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 01:59 UTCEPSS rescore
  42. 2026-07-15 01:59 UTCEPSS rescore
  43. 2026-07-13 22:29 UTCEPSS rescore
  44. 2026-07-13 06:12 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-09 19:09 UTCEPSS rescore
  48. 2026-07-08 15:15 UTCEPSS rescore
  49. 2026-07-07 13:46 UTCEPSS rescore
  50. 2026-07-06 16:27 UTCEPSS rescore
  51. 2026-07-06 16:27 UTCEPSS rescore
  52. 2026-07-06 09:11 UTCOSV refresh
  53. 2026-07-06 02:23 UTCEPSS rescore
  54. 2026-07-06 02:23 UTCEPSS rescore
  55. 2026-07-05 02:30 UTCEPSS rescore
  56. 2026-07-05 02:30 UTCEPSS rescore
  57. 2026-07-04 06:31 UTCEPSS rescore
  58. 2026-07-04 06:30 UTCEPSS rescore
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-07-01 15:06 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-29 14:06 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-28 14:07 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 04:56 UTCEPSS rescore
  67. 2026-06-28 04:55 UTCEPSS rescore
  68. 2026-06-27 03:08 UTCEPSS rescore
  69. 2026-06-25 13:49 UTCEPSS rescore
  70. 2026-06-24 14:04 UTCEPSS rescore
  71. 2026-06-24 14:04 UTCEPSS rescore
  72. 2026-06-24 10:01 UTCNVD updateCVSS v3 → 8.8
  73. 2026-06-23 21:32 UTCEPSS rescore
  74. 2026-06-23 21:32 UTCEPSS rescore
  75. 2026-06-22 14:25 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-66448?
CVE-2025-66448 is a high vulnerability published on December 1, 2025. vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.11.1, vllm has a critical remote code execution vector in a config class named NemotronNanoVLConfig. When vllm loads a model config that contains an automap entry, the config class resolves that mapping with…
When was CVE-2025-66448 disclosed?
CVE-2025-66448 was first published in the National Vulnerability Database on December 1, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-66448 actively exploited?
CVE-2025-66448 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all scored CVEs.
What is the CVSS score of CVE-2025-66448?
CVE-2025-66448 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-66448?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-66448, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-66448

Explore →

Is Your Infrastructure Affected by CVE-2025-66448?

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

Start Free Scan →Browse All CVEs