Disclosed weakness · no CVE recorded

LiteLLM could send an embeddings request and its credential to an unintended host

LiteLLM · LiteLLM SDK and Proxy · Cohere embeddings

First documented disclosure · Review checkpoint

Summary

Embedding requests intended for a private gateway could go directly to Cohere’s public endpoint with the configured gateway key.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reporter and maintainer document incorrect routing. The cited sources report no malicious use of the transmitted key.

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 embeddings adapter ignored the configured base URL from the process environment when no explicit request base was supplied.

Conditions required

A deployment points Cohere requests at an internal gateway through the process environment and omits an explicit base on the embedding call.

Potential impact

The public endpoint could receive embedding input and a credential intended for the internal gateway.

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

Configure an explicit embedding endpoint or deploy the fix. Review affected requests and rotate gateway keys that went to the unintended destination.

Operating lesson

Bind each provider credential to the endpoint authorized to receive it.

Evidence and limits

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

Sources