CVE-2026-48746

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2%, top 36% 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 — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). From 0.3.0 until 0.22.0, a vulnerability in ASGI web servers and starlette's trust on those web servers enables an authentication bypass of the OpenAI API AuthenticationMiddleware. It allows to use the API without providing the configured VLLM_API_KEY or --api-key. This vulnerability is fixed in 0.22.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
64%
KEV
Not listed

Published

June 16, 2026

Last Modified

August 19, 2026

Advisory Details (10)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github, redhat.
generic🟡 PoC Available

Advisory X41-2026-002: Request Host Header not Validated in Starlette | X41 D-Sec - Penetration Tests and Source Code Audits

https://x41-dsec.de/lab/advisories/x41-2026-002-starlette
github Patch Available

OpenAI API Auth Bypass · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-94f4-hr76-p5j6
github_pr

[Frontend] Simplify AuthenticationMiddleware path extraction

Fix merged in vllm-project/vllm PR #43426 on 2026-05-22 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/43426

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat
redhatrhoai/odh-caikit-tgis-serving-rhel9:17830824302026-07-21redhat
redhatansible-automation-platform-26/mcp-tools-rhel9:17839206402026-07-20redhat
redhatansible-automation-platform-27/mcp-tools-rhel9:17839184032026-07-20redhat
redhatrhaiis/vllm-rocm-rhel9:17829512442026-07-06redhat
redhatrhaiis/vllm-cuda-rhel9:17829510122026-07-06redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat

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.10.0 ... 0.9.2 (68 versions)0.22.0

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 42× in last 7d / 173× 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 304 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48746?
CVE-2026-48746 is a critical vulnerability published on June 16, 2026. vLLM is an inference and serving engine for large language models (LLMs). From 0.3.0 until 0.22.0, a vulnerability in ASGI web servers and starlette's trust on those web servers enables an authentication bypass of the OpenAI API AuthenticationMiddleware. It allows to use the API without providing…
When was CVE-2026-48746 disclosed?
CVE-2026-48746 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48746 actively exploited?
CVE-2026-48746 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 35.5% of all scored CVEs.
What is the CVSS score of CVE-2026-48746?
CVE-2026-48746 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48746?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48746, 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-48746

Explore →

Is Your Infrastructure Affected by CVE-2026-48746?

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