CVE-2026-41523

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% 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, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, an assert-based security check in vLLM's activation function loading allows any unauthenticated attacker to achieve arbitrary code execution on the server by publishing a malicious HuggingFace model, when vLLM runs in Python optimized mode (python -O or PYTHONOPTIMIZE=1). This vulnerability is fixed in 0.22.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

Published

June 16, 2026

Last Modified

September 4, 2026

Advisory Details (3)

Auto-updated Jun 23, 2026
Patch available. Sources: github, github_commit.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/dcb05b04-e625-41e7-adbc-bbae0cc2d64c
github_commit

commit b3c7ffcab82c (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/b3c7ffcab82c2439726f8cb213800f6f38c023d3
github Patch Available

Security Check Bypass via assert Statement in Activation Function Loading Allows Arbitrary Code Execution · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-q8gq-377p-jq3r

Vendor Advisories for CVE-2026-41523(20)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhelai3/bootc-rocm-rhel9:17882606202026-09-01redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-rocm-rhel9:17871618032026-08-24redhat
redhatrhelai3/disk-image-cuda-rhel9:17873107172026-08-24redhat
redhatrhaiis/vllm-cuda-rhel9:17871613822026-08-24redhat
redhatrhelai3/bootc-rocm-rhel9:17872440062026-08-24redhat
redhatrhaii/vllm-cuda-rhel9:17871517712026-08-20redhat
redhatrhaii/vllm-rocm-rhel9:17871517742026-08-20redhat
redhatrhaii/vllm-cpu-rhel9:17871517692026-08-20redhat
redhatrhaii/vllm-spyre-rhel9:17871518402026-08-20redhat
redhatrhaiis/vllm-rocm-rhel9:17829512442026-07-06redhat
redhatrhaiis/vllm-cuda-rhel9:17829510122026-07-06redhat

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 rangeFix by version rangeDependents
vllm0.0.1 ... 0.9.2 (86 versions)
  • every version up to 0.22.0: fixed in 0.22.0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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 221 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41523?
CVE-2026-41523 is a high vulnerability published on June 16, 2026. vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, an assert-based security check in vLLM's activation function loading allows any unauthenticated attacker to achieve arbitrary code execution on the server by publishing a malicious HuggingFace model, when…
When was CVE-2026-41523 disclosed?
CVE-2026-41523 was first published on June 16, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41523 actively exploited?
CVE-2026-41523 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41523?
CVE-2026-41523 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-41523?
A fix for CVE-2026-41523 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41523 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-41523

Explore →

Is Your Infrastructure Affected by CVE-2026-41523?

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

Book a Demo →Browse All CVEs