Disclosed weakness · no CVE recorded

A restricted LiteLLM key could create an unrelated customer organization record

LiteLLM · LiteLLM Proxy · customer organization registration

First documented disclosure · Review checkpoint

Summary

A request made with a key pinned to one customer organization could register another organization alias before the proxy refused it.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The maintainer documented the unwanted write in a controlled check and identified no malicious use.

Exploitation evidence source

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 proxy wrote an unfamiliar organization alias before it checked whether the key could act for that organization.

Conditions required

A caller has an organization-pinned key on a build with automatic alias registration.

Potential impact

Unauthorized organization records could accumulate in the administrative inventory. The published example shows the underlying request was denied.

Affected versions and configurations

The maintainer attributes the regression to development change #51637. A numbered affected release was not established.

Fix and mitigation status

LiteLLM lists the fix in its development release 1.111.0-dev.4.

Practical next steps

Deploy the corrected registration order and review unexpected customer organization aliases created by denied requests.

Operating lesson

Complete authorization before creating records on behalf of a caller.

Evidence and limits

The maintainer documents a correction. The cited sources provide no issue-specific severity rating or CVE.

Sources