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 35% 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
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.2%CVSS: 9.1Exploit: Elevated riskExposed services: Not assessed

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.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

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%
EPSS PROB
1.2%
EPSS %ILE
65th
KEV
Not listed

Published

June 16, 2026

Last Modified

September 16, 2026

Advisory Details (10)

Auto-updated Sep 15, 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(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhoai/odh-caikit-tgis-serving-rhel9:17830824302026-07-21redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat
redhatansible-automation-platform-26/mcp-tools-rhel9:17839206402026-07-20redhat
redhatansible-automation-platform-27/mcp-tools-rhel9:17839184032026-07-20redhat
redhatrhaiis/vllm-cuda-rhel9:17829510122026-07-06redhat
redhatrhaiis/vllm-rocm-rhel9:17829512442026-07-06redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-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 rangeFix by version rangeDependents
vllm0.10.0 ... 0.9.2 (68 versions)
  • 0.3.0 up to 0.22.0: fixed in 0.22.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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 359 total refreshes for this CVE.

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

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 on June 16, 2026, with the most recent update on September 16, 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.2% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48746?
CVE-2026-48746 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48746?
A fix for CVE-2026-48746 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48746 are linked in the Vendor Advisories panel on this page.

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.