Disclosed weakness · no CVE recorded

LiteLLM error-log suppression could drop billable usage

LiteLLM · LiteLLM Proxy · failed-request spend accounting

First documented disclosure · Review checkpoint

Summary

Turning off detailed error logs also suppressed known charges for some failed requests.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: Reviewed maintainer reports and controlled checks do not establish malicious exploitation against users.

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 spend-tracking gate treated disabled error logging as a reason to skip failures with billable usage or charged retry attempts.

Conditions required

The operator sets disable_error_logs to true and a request incurs a recoverable charge before failing, such as an interrupted stream, billed timeout or charged guardrail failure.

Potential impact

Tracked spend can understate actual provider charges and weaken spending controls that depend on those counters.

Affected versions and configurations

The original reporter identifies LiteLLM 1.108.10. Affected pre-fix source builds are also demonstrated; a complete released-version range is not established.

Fix and mitigation status

PR53271 is present in prerelease 1.112.0-dev.2. No corrected stable release or historical usage repair is established.

Practical next steps

Use a verified correction or retain the accounting path while suppressing only detailed error records. Reconcile earlier charges with provider records.

Operating lesson

Logging preferences must not disable financial enforcement or usage accounting.

Evidence and limits

The original public issue is November 20; the corrective PR and development release are November 21. The maintainer reports controlled two-worker PostgreSQL/Redis checks, including synthetic failures and a real-provider case. The fix retains known billed failures; zero-cost errors, finalized costs and explicitly disabled spend updates keep their existing behavior. It does not establish recovery of unknown usage or backfill historical charges. No malicious exploitation or security score was reported.

Sources