Critical [CVE-2026-48746] Critical authentication bypass allows unauthorized API access
This critical-severity Red Hat Linux advisory covers CVE-2026-48746 affecting Red Hat AI Inference Server 3.2, Red Hat AI Inference Server 3.3, Red Hat AI Inference Server 3.4.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
CVE-2026-48746 is an authentication bypass in the vLLM OpenAI-compatible API server. A remote attacker who can reach the vLLM endpoint directly can craft a Host header so the authentication middleware checks a different URL path than the one actually dispatched, bypassing VLLM_API_KEY / --api-key protection.
Successful exploitation allows unauthorized inference API access, which can result in confidentiality loss (model/prompt abuse) and availability impact (resource exhaustion). The flaw does not provide integrity compromise or arbitrary code execution.
Exploitation requires vLLM API-key authentication to be enabled and the service to be exposed without an RFC-conforming reverse proxy that normalizes the Host header.
Because Red Hat AI inference offerings are commonly deployed behind OpenShift Routes or similar proxies, and because the vulnerability is conditional on deployment and configuration, the overall flaw impact is rated Important rather than Critical.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 0.22.0
- rhaiis/vllm-cuda-rhel9:1782951012
- rhaiis/vllm-rocm-rhel9:1782951244
- rhaiis/vllm-cuda-rhel9:1787860580
- rhaiis/vllm-rocm-rhel9:1787884873
- rhaiis/vllm-rocm-rhel9:1782353093
- rhaiis/vllm-cuda-rhel9:1782352847
- rhaii/vllm-spyre-rhel9:1789681201
- rhaii/vllm-cpu-rhel9:1789681128
- rhaii/vllm-cuda-rhel9:1789681126
- rhaii/vllm-rocm-rhel9:1789681126
- ansible-automation-platform-26/mcp-tools-rhel9:1783920640
- ansible-automation-platform-27/mcp-tools-rhel9:1783918403
- mta/mta-solution-server-rhel9:1784109883
- rhoai/odh-caikit-tgis-serving-rhel9:1783082430
- RHSA-2026:36005
- RHSA-2026:36006
- RHSA-2026:61627
- RHSA-2026:61629
- RHSA-2026:30088
- RHSA-2026:30089
- RHSA-2026:69464
- RHSA-2026:69466
- RHSA-2026:69467
- RHSA-2026:69469
- RHSA-2026:42132
- RHSA-2026:42142
- RHSA-2026:43038
- RHSA-2026:42644
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- Restrict network access to the vLLM API endpoint to only trusted clients and internal networks. Implement firewall rules or network policies to limit inbound connections to the vLLM service, thereby reducing the attack surface. This operational control helps prevent unauthorized external access to the vulnerable API.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.