CVE-2026-48746

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 46% 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: cna:github_m, epss
Trending — 3 sources updated this weekElevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 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)
EPSS
54.1%
KEV
Not listed

Published

June 16, 2026

Last Modified

July 3, 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(5)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
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 72× in last 7d / 170× 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 170 total refreshes for this CVE.

  1. 2026-07-06 23:11 UTCEG score recompute
  2. 2026-07-06 23:11 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 06:48 UTCEG score recompute
  5. 2026-07-06 06:48 UTCVendor advisory
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 01:47 UTCEG score recompute
  8. 2026-07-06 01:47 UTCVendor advisory
  9. 2026-07-05 21:30 UTCEG score recompute
  10. 2026-07-05 21:30 UTCVendor advisory
  11. 2026-07-05 17:14 UTCEG score recompute
  12. 2026-07-05 17:14 UTCVendor advisory
  13. 2026-07-05 12:58 UTCEG score recompute
  14. 2026-07-05 12:58 UTCVendor advisory
  15. 2026-07-05 08:42 UTCEG score recompute
  16. 2026-07-05 08:42 UTCVendor advisory
  17. 2026-07-05 03:08 UTCEG score recompute
  18. 2026-07-05 03:08 UTCVendor advisory
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 22:50 UTCEG score recompute
  21. 2026-07-04 22:50 UTCVendor advisory
  22. 2026-07-04 18:34 UTCEG score recompute
  23. 2026-07-04 18:34 UTCVendor advisory
  24. 2026-07-04 13:26 UTCEG score recompute
  25. 2026-07-04 13:26 UTCVendor advisory
Show 75 more
  1. 2026-07-04 09:10 UTCEG score recompute
  2. 2026-07-04 09:10 UTCVendor advisory
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-03 22:42 UTCEG score recompute
  5. 2026-07-03 22:42 UTCVendor advisory
  6. 2026-07-03 18:23 UTCEG score recompute
  7. 2026-07-03 18:23 UTCVendor advisory
  8. 2026-07-03 13:48 UTCEG score recompute
  9. 2026-07-03 13:48 UTCVendor advisory
  10. 2026-07-03 09:15 UTCEG score recompute
  11. 2026-07-03 09:15 UTCVendor advisory
  12. 2026-07-03 04:58 UTCEG score recompute
  13. 2026-07-03 04:58 UTCVendor advisory
  14. 2026-07-03 00:37 UTCEG score recompute
  15. 2026-07-03 00:37 UTCVendor advisory
  16. 2026-07-02 20:18 UTCEG score recompute
  17. 2026-07-02 20:18 UTCVendor advisory
  18. 2026-07-02 16:02 UTCEG score recompute
  19. 2026-07-02 16:02 UTCVendor advisory
  20. 2026-07-02 11:46 UTCEG score recompute
  21. 2026-07-02 11:46 UTCVendor advisory
  22. 2026-07-02 07:15 UTCEG score recompute
  23. 2026-07-02 07:15 UTCVendor advisory
  24. 2026-07-02 02:56 UTCEG score recompute
  25. 2026-07-02 02:56 UTCVendor advisory
  26. 2026-07-01 22:39 UTCEG score recompute
  27. 2026-07-01 22:39 UTCVendor advisory
  28. 2026-07-01 18:05 UTCEG score recompute
  29. 2026-07-01 18:05 UTCVendor advisory
  30. 2026-07-01 15:07 UTCEPSS rescore
  31. 2026-07-01 13:49 UTCEG score recompute
  32. 2026-07-01 13:49 UTCVendor advisory
  33. 2026-07-01 09:33 UTCEG score recompute
  34. 2026-07-01 09:33 UTCVendor advisory
  35. 2026-07-01 05:17 UTCEG score recompute
  36. 2026-07-01 05:17 UTCVendor advisory
  37. 2026-07-01 01:01 UTCEG score recompute
  38. 2026-07-01 01:01 UTCVendor advisory
  39. 2026-06-30 23:22 UTCEPSS rescore
  40. 2026-06-30 20:44 UTCEG score recompute
  41. 2026-06-30 20:44 UTCVendor advisory
  42. 2026-06-30 16:27 UTCEG score recompute
  43. 2026-06-30 16:27 UTCVendor advisory
  44. 2026-06-30 12:10 UTCEG score recompute
  45. 2026-06-30 12:10 UTCVendor advisory
  46. 2026-06-30 06:23 UTCEG score recompute
  47. 2026-06-30 06:23 UTCVendor advisory
  48. 2026-06-30 02:06 UTCEG score recompute
  49. 2026-06-30 02:06 UTCVendor advisory
  50. 2026-06-29 21:50 UTCEG score recompute
  51. 2026-06-29 21:50 UTCVendor advisory
  52. 2026-06-29 17:34 UTCEG score recompute
  53. 2026-06-29 17:34 UTCVendor advisory
  54. 2026-06-29 14:06 UTCEPSS rescore
  55. 2026-06-29 14:06 UTCEPSS rescore
  56. 2026-06-29 13:01 UTCEG score recompute
  57. 2026-06-29 13:01 UTCVendor advisory
  58. 2026-06-29 08:43 UTCEG score recompute
  59. 2026-06-29 08:43 UTCVendor advisory
  60. 2026-06-29 04:20 UTCEG score recompute
  61. 2026-06-29 04:20 UTCVendor advisory
  62. 2026-06-28 23:49 UTCEG score recompute
  63. 2026-06-28 23:49 UTCVendor advisory
  64. 2026-06-28 19:32 UTCEG score recompute
  65. 2026-06-28 19:32 UTCVendor advisory
  66. 2026-06-28 15:16 UTCEG score recompute
  67. 2026-06-28 15:16 UTCVendor advisory
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 10:50 UTCEG score recompute
  70. 2026-06-28 10:50 UTCVendor advisory
  71. 2026-06-28 06:33 UTCEG score recompute
  72. 2026-06-28 06:33 UTCVendor advisory
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-28 04:56 UTCEPSS rescore
  75. 2026-06-28 02:18 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 in the National Vulnerability Database on June 16, 2026, with the most recent update on July 3, 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 54.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48746?
CVE-2026-48746 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
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