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 — Patch released 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

July 22, 2026

Advisory Details (3)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr.
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_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
github Patch Available

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

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

Vendor Advisories for CVE-2026-48746(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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 12× in last 7d / 135× 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 141 total refreshes for this CVE.

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

Start Free Scan →Browse All CVEs