CVE-2026-73558

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 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. Prior to 0.27.0, an integer overflow in blockIdx.x * 2 * d in activation_kernels.cu can cause act_and_mul_kernel to consume another batched user's input, allowing a request processed in the same inference batch to receive a partial or complete copy of another user's inference result. This issue is fixed in version 0.27.0.

CVSS v3
5.3
EG Score
5.3(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
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Cross-User Data Leak Vulnerability · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-7m6h-x95x-82q5
github_release Patch Available

v0.27.0

Patch available: vllm-project/vllm v0.27.0

https://github.com/vllm-project/vllm/releases/tag/v0.27.0
github_pr

[Bugfix][Kernel] Fix integer overflow in libtorch_stable/activation_kernels.cu

Fix merged in vllm-project/vllm PR #49660 on 2026-07-30 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/49660
generic

[Bug]: integer overflow in activation_kernels.cu · Issue #42860 · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/issues/42860
github_commit

commit 451227cb3ff0 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/451227cb3ff07989698fed982c2d3e4300257924

Vendor Advisories for CVE-2026-73558(1)

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 (93 versions)0.27.0

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-73558?
CVE-2026-73558 is a medium vulnerability published on August 13, 2026. vLLM is an inference and serving engine for large language models. Prior to 0.27.0, an integer overflow in blockIdx.x 2 d in activationkernels.cu can cause actandmulkernel to consume another batched user's input, allowing a request processed in the same inference batch to receive a partial or…
When was CVE-2026-73558 disclosed?
CVE-2026-73558 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73558 actively exploited?
CVE-2026-73558 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.1% of all scored CVEs.
What is the CVSS score of CVE-2026-73558?
CVE-2026-73558 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-73558?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73558, 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-73558

Explore →

Is Your Infrastructure Affected by CVE-2026-73558?

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