CVE-2026-41523

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

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.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

June 16, 2026

Last Modified

July 22, 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(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-cuda-rhel9:17829510122026-07-06redhat
redhatrhaiis/vllm-rocm-rhel9:17829512442026-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 rangeFixed inDependents
vllm0.0.1 ... 0.9.2 (86 versions)0.22.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 58× 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-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 07:38 UTCVendor advisory
  3. 2026-07-26 19:51 UTCEG score recompute
  4. 2026-07-26 19:51 UTCVendor advisory
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:11 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 02:29 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-16 22:40 UTCVendor advisory
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 03:14 UTCVendor advisory
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 15:28 UTCVendor advisory
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-15 01:17 UTCVendor advisory
  25. 2026-07-14 11:44 UTCVendor advisory
Show 39 more
  1. 2026-07-13 22:50 UTCVendor advisory
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 11:05 UTCVendor advisory
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 22:14 UTCVendor advisory
  7. 2026-07-12 10:29 UTCVendor advisory
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 22:43 UTCVendor advisory
  10. 2026-07-11 10:58 UTCVendor advisory
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-10 23:11 UTCVendor advisory
  13. 2026-07-10 11:19 UTCVendor advisory
  14. 2026-07-09 22:52 UTCVendor advisory
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 11:04 UTCVendor advisory
  17. 2026-07-08 23:04 UTCVendor advisory
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-08 11:17 UTCVendor advisory
  20. 2026-07-07 23:29 UTCVendor advisory
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-07 11:44 UTCVendor advisory
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
  26. 2026-07-06 02:23 UTCEPSS rescore
  27. 2026-07-05 02:30 UTCEPSS rescore
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-01 15:06 UTCEPSS rescore
  30. 2026-06-30 23:22 UTCEPSS rescore
  31. 2026-06-29 14:06 UTCEPSS rescore
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-27 03:08 UTCEPSS rescore
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-25 13:49 UTCEPSS rescore
  37. 2026-06-24 14:05 UTCEPSS rescore
  38. 2026-06-23 21:33 UTCEPSS rescore
  39. 2026-06-16 17:47 UTCEG score recompute

Related CVEs(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 in the National Vulnerability Database on June 16, 2026, with the most recent update on July 22, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 49.0% of all scored CVEs.
What is the CVSS score of CVE-2026-41523?
CVE-2026-41523 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41523?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41523, 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-41523

Explore →

Is Your Infrastructure Affected by CVE-2026-41523?

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

Start Free Scan →Browse All CVEs