Disclosed weakness · no CVE recorded
LiteLLM could leave a user’s keys active after a failed SCIM deactivation
LiteLLM · LiteLLM Proxy · SCIM user provisioning
First documented disclosure · Review checkpoint
Summary
The proxy could reject an identity provider’s deactivation request when the same update named a group with no matching LiteLLM team. The account and its keys remained active.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The maintainer documented the failed deactivation and working keys. The sources report no malicious use of retained 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
Group reconciliation aborted the user update before the proxy applied deactivation and blocked the keys.
Conditions required
SCIM deprovisioning includes a group identifier that has no corresponding team in LiteLLM.
Potential impact
A user intended for deactivation could continue using existing keys while the failed update remained unresolved.
Affected versions and configurations
The maintainer traces the regression to 1.99.0. The full set of affected release branches is unspecified.
Fix and mitigation status
LiteLLM lists the fix in its development release 1.111.0-dev.4.
Practical next steps
Deploy a build containing the SCIM fix. Reconcile failed deprovisioning events with actual account and key status.
Operating lesson
Check the effective status of accounts and credentials after a provisioning error.
Evidence and limits
The maintainer documents a correction. The cited sources provide no issue-specific severity rating or CVE.
Sources
- LiteLLM maintainer fix #51829
Primary source ·
- LiteLLM v1.111.0-dev.4 release notes
Primary source ·