Disclosed weakness · no CVE recorded
LiteLLM could route a team’s WebSocket request outside its permitted model group
LiteLLM · LiteLLM Proxy · Responses WebSocket routing
First documented disclosure · Review checkpoint
Summary
A team’s model alias could select a shared deployment outside the team’s assigned group.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The reporter found misrouted traffic in its own deployment. The cited sources do not identify deliberate abuse.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The WebSocket handler replaced the model name after authorization, discarding the deployment alias selected for the team.
Conditions required
A team uses an alias to restrict deployment selection and a shared deployment serves the same upstream model.
Potential impact
Requests could reach a provider deployment with different credentials, billing or data-handling arrangements.
Affected versions and configurations
The reporter confirmed 1.110.0-rc.1 and a main-branch build. The earliest affected version is unknown.
Fix and mitigation status
LiteLLM lists the fix in its release candidate 1.110.0-rc.3.
Practical next steps
Deploy a build containing the routing fix. Review WebSocket request logs for deployment IDs outside each team’s allowed groups.
Operating lesson
Apply deployment restrictions to the final routing decision for each transport.
Evidence and limits
The maintainer documents a correction. The cited sources provide no issue-specific severity rating or CVE.
Sources
- LiteLLM public issue #51379
Primary source ·
- LiteLLM maintainer fix #51380
Primary source ·
- LiteLLM release-branch backport #51854
Primary source ·
- LiteLLM v1.110.0-rc.3 release notes
Primary source ·