Disclosed weakness · no CVE recorded

LiteLLM long-form budget durations could refill spending limits every night

LiteLLM · LiteLLM Proxy · budget resets

First documented disclosure · Review checkpoint

Summary

Some accepted long-form durations scheduled the next budget reset for midnight instead of the intended period.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed sources describe a correction or controlled reproduction; malicious exploitation against users is not established.

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

Budget validation and reset scheduling interpreted unit spellings differently.

Conditions required

An administrator configures a duration such as 1month, 7days or 2weeks and relies on the resulting spending cap.

Potential impact

A multi-day budget can refill too soon, permitting spending above the intended period limit.

Affected versions and configurations

The reviewed sources do not establish a complete affected-release range.

Fix and mitigation status

1.109.2 corrects supported long unit spellings. Multi-month long forms remain outside that correction in the reviewed tag.

Practical next steps

Use a verified supported duration and inspect stored reset timestamps; do not assume 12months or another multi-month spelling is repaired.

Operating lesson

Use the same duration interpretation when accepting and enforcing a spending policy.

Evidence and limits

The November 13 PR describes a broader main-branch correction, including 12months. The reviewed 1.109.2 tag instead preserves long month spellings when the count is not one and supports only single-month standardized resets; those forms still fall back to midnight. The stable release must not be described as fixing every example in the PR.

Sources