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.7%, top 48% 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
Trending — Patch released 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
52%
KEV
Not listed

Published

June 16, 2026

Last Modified

August 20, 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(6)

Vendor / EcosystemFixed in / PatchReleasedSource
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-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.

Additional Vendor Advisories

(4)

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 25× in last 7d / 100× 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 153 total refreshes for this CVE.

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

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 August 20, 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 48.0% of all scored CVEs.
What is the CVSS score of CVE-2026-41523?
CVE-2026-41523 has a CVSS v3 base score of 7.5 (NVD).
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