Disclosed weakness · no CVE recorded
LiteLLM MCP clients could receive access to servers deselected during sign-in
LiteLLM · LiteLLM Proxy · MCP gateway sign-in
First documented disclosure · Review checkpoint
Summary
The MCP connection page let users deselect servers, but the resulting client credential still covered servers the user had excluded.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The maintainer documented the consent mismatch and the fix. The cited sources report no hostile access.
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 sign-in flow discarded the server selections when issuing the client credential.
Conditions required
A user completes gateway sign-in for an MCP client and deselects at least one server the user can otherwise access.
Potential impact
A connected client could reach more of the user’s authorized MCP servers than the user intended to delegate.
Affected versions and configurations
The public fix identifies the affected implementation. The full affected version range is unspecified.
Fix and mitigation status
LiteLLM lists the fix in its development release 1.111.0-dev.4.
Practical next steps
Deploy the sign-in scope fix and reauthorize clients that should have narrower access.
Operating lesson
Carry the user’s selected resources through consent, token issuance and enforcement.
Evidence and limits
The maintainer documents a correction. The cited sources provide no issue-specific severity rating or CVE.
Sources
- LiteLLM maintainer fix #50973
Primary source ·
- LiteLLM v1.111.0-dev.4 release notes
Primary source ·