CVE-2026-27893

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.3%, top 31% 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: cna:github_m, epss
Trending — 3 sources updated this week
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). Starting in version 0.10.1 and prior to version 0.18.0, two model implementation files hardcode trust_remote_code=True when loading sub-components, bypassing the user's explicit --trust-remote-code=False security opt-out. This enables remote code execution via malicious model repositories even when the user has explicitly disabled remote code trust. Version 0.18.0 patches the issue.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
69%
KEV
Not listed

Published

March 27, 2026

Last Modified

July 27, 2026

Advisory Details (10)

Auto-updated Jun 30, 2026
Patch available. Sources: github_commit, github_pr, github, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:8746
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24977
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19725
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19724
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19712
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10141
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10140
github Patch Available

Hardcoded trust_remote_code=True in NemotronVL and KimiK25 bypasses user security opt-out · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-7972-pg2x-xr59
github_pr

[Security] Respect user trust_remote_code setting in NemotronVL and KimiK25

Fix merged in vllm-project/vllm PR #36192 on 2026-03-06 — awaiting tagged release

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

commit 00bd08edeee5 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/00bd08edeee5dd4d4c13277c0114a464011acf72

Vendor Advisories for CVE-2026-27893(12)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-vllm-rocm-rhel9:17839988572026-07-21redhat
redhatrhoai/odh-vllm-cpu-rhel9:17829960802026-07-09redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17800690692026-06-10redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17786001872026-05-20redhat
redhatrhaiis/vllm-rocm-rhel9:17792236512026-05-20redhat
redhatrhaiis/vllm-cuda-rhel9:17792236542026-05-20redhat
redhatrhelai3/disk-image-cuda-rhel9:17769388712026-04-23redhat
redhatrhelai3/bootc-rocm-rhel9:17767735052026-04-23redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-04-17redhat
redhatrhaiis/vllm-cuda-rhel9:17756801922026-04-17redhat
redhatrhaiis/model-opt-cuda-rhel9:17757498572026-04-17redhat

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.10.1 ... 0.17.1 (15 versions)0.18.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-27893?
CVE-2026-27893 is a high vulnerability published on March 27, 2026. vLLM is an inference and serving engine for large language models (LLMs). Starting in version 0.10.1 and prior to version 0.18.0, two model implementation files hardcode trustremotecode=True when loading sub-components, bypassing the user's explicit --trust-remote-code=False security opt-out. This…
When was CVE-2026-27893 disclosed?
CVE-2026-27893 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27893 actively exploited?
CVE-2026-27893 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 30.8% of all scored CVEs.
What is the CVSS score of CVE-2026-27893?
CVE-2026-27893 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-27893?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27893, 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-2026-27893

Explore →

Is Your Infrastructure Affected by CVE-2026-27893?

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

Start Free Scan →Browse All CVEs