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.5%, top 63% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
36.9%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 30, 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.

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

Related CVEs(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 June 30, 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 36.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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